This is 10x secure than your normal Javascript obfuscator and different and yes you also have to adapt to It's environment and on how it works.
This does not work in browser but It's secure even If the code can be seen locally(If you don't want to, use pkg).
Feel free to suggests or give your feedbacks.
Hidden Content
Rest assured that we do not log anything. You can also implement for extra security.
Demo/Example:
1. Visit
2. Get the response and put it in **encLink** query
3. Code:
(async()=>{
"use strict";
// Dependencies
const request = require("request-async")
const byteNode = require("bytenode")
// Variables
global.require = require
// Main
var response = await request(" ")
response = response.body
byteNode.runBytecode(new Buffer.from(response, "hex"))
})()
4. it's required to always use Node v16.16.0 and you might ask what is the global.require for? Because bytenode runs the code using node:vm and in order to require packages you need it.
This does not work in browser but It's secure even If the code can be seen locally(If you don't want to, use pkg).
Feel free to suggests or give your feedbacks.
Hidden Content
Rest assured that we do not log anything. You can also implement for extra security.
Demo/Example:
1. Visit
2. Get the response and put it in **encLink** query
3. Code:
(async()=>{
"use strict";
// Dependencies
const request = require("request-async")
const byteNode = require("bytenode")
// Variables
global.require = require
// Main
var response = await request(" ")
response = response.body
byteNode.runBytecode(new Buffer.from(response, "hex"))
})()
4. it's required to always use Node v16.16.0 and you might ask what is the global.require for? Because bytenode runs the code using node:vm and in order to require packages you need it.