A really secure Javascript obfuscator

Ernestbok

Well-known member
Member
Joined
3 yrs. 4 mth. 13 days
Messages
3,934
Reaction score
5,775
Wallet
0$
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
Please, Log in or Register to view URLs content!
for extra security.



Demo/Example:

1. Visit
Please, Log in or Register to view URLs content!


2. Get the response and put it in **encLink** query

Please, Log in or Register to view URLs content!




3. Code:

(async()=>{
"use strict";

// Dependencies
const request = require("request-async")
const byteNode = require("bytenode")

// Variables
global.require = require

// Main
var response = await request("
Please, Log in or Register to view URLs content!
")
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.
 
Paid adv. expire in 2 months
CLICK to buy Advertisement !
westernunion carding Verified & Trusted WesternUnion | MoneyGram | Bank - Transferring [299$ BTC for 2000$ WU]
electronics carding Verified & Trusted Electronics Carding, Carding iPhone, Samsung Carding, MacBook Carding, Laptops Carding

Tornado

[ Final Boss ]
Staff member
Escrow
Moderator
Administrator
V.I.P
Joined
12 yrs. 10 mth. 18 days
Messages
8,339
Reaction score
27,857
Wallet
8,991$
Please, Log in or Register to view quote content!
This seems like a very interesting approach to obfuscation. However, I do have some questions and concerns.

Firstly, I understand that the code is not meant to be executed in a browser, but if the code can be seen locally, wouldn't it be susceptible to reverse engineering?

Secondly, while I agree that not logging anything is a good security practice, what measures are in place to prevent attackers from accessing and abusing the service?

Overall, I appreciate the effort put into creating this and would be interested to hear more about how it works and its limitations.
 
Top Bottom