Re:JSFuck (2012)
by slig on Saturday September 25, 2021 @11:13PM
(#28658114)
I'm curious: can you can undo the obfuscation of JScrambler and Obfuscator.io easily? Some time ago I tried to run both through Closure Compiler, but it was way harder than I thought would be.
[ Parent
| on HN ]
JScrambler I actually did de-obfuscate to bypass some very significant bot detection a few years ago, but it took a bit more doing -- it uses ES6 features IIRC so I had to transpile it down to ES5 via babel first, but it worked OK after that.
has a pretty good crack at obfuscator.io, too: https://closure-compiler.appspot.com/home#code%3D%252F%252F%...
That's the example from the site. "console.log('Hello world')" gets deobfuscated to "console[a(482)]("Hello World!");"
> That's the example from the site. "console.log('Hello world')" gets deobfuscated to "console[a(482)]("Hello World!");"
That does not look deobfuscated to me.
Re:JSFuck (2012)
by ByteJockey on Sunday September 26, 2021 @11:16AM
(#28661512)
Anyone familiar with JS is going to have some really good guesses at what a(482) is in this case.
And, even if you don't, you can always call a(482)
Yes, but "obfuscated" means "To make so confused or opaque as to be difficult to perceive or understand". That's obfuscated, not deobfuscated.
Re:JSFuck (2012)
by AlexAndScripts on Monday September 27, 2021 @08:26AM
(#28669788)
Is that difficult? Harder, but still quite easy.
My point was that the GP seems to have mixed the words "obfuscate" and "deobfuscate".
To clarify, that's what happens once you pass it through the obfuscation and THEN closure compiler. If you click the link you will see the obfuscation is much more complex