News for hackers. Stuff that matters.
Re:JSNice: Statistical renaming, type inference, and deobfus... by dsp1234 on Tuesday November 15, 2016 @12:14PM (#12959987)
Just as a general thought, not specific to this product:

This is decrypted and eval'd at runtime

Most(all?) string-based obfuscators can be bypassed by simply replacing eval with a logging eval implementation.

  var oldEval = eval; eval = function(str){console.log(str);oldEval(str)};
A similar patch to the Function constructor can bypass the other easy dynamic code generation code path.

If at some point, a string needs to be evaluated as code, then it's possible to intercept that code and output it.

Re:JSNice: Statistical renaming, type inference, and deobfus... by slig on Tuesday November 15, 2016 @06:06PM (#12963142)
That didn't work on JScrambler. The function that does the decryption checks to see if the `eval` has been tampered. (IIRC it checks for a `prototype` property). And you can't modify the body of this function otherwise the decryption fails.
Re:JSNice: Statistical renaming, type inference, and deobfus... by visarga on Tuesday November 15, 2016 @01:02PM (#12960430)
So, all you need is to break a longer eval into multiple smaller ones, shuffle them and thus make it a chore to connect the evals back.
Re:JSNice: Statistical renaming, type inference, and deobfus... by r0ckcg on Wednesday November 16, 2016 @12:46PM (#12969403)
tried it, does not work I'm afraid...