[VXAZ]

Hello Everyone!
I present to you all a challenge designed for experienced JavaScript reverse engineers! I hope that you enjoy deobfuscating this file as much as I enjoyed writing the algorithm that obfuscated the source. If you do successfully recover the source code please reply or PM me with the source and the estimated time it took you to fully recover the source!
IMPORTANT INFORMATION: the source code is not malicious
------------------------------------
Domain: kelloggs-test.glitch.me
Challenge-Resource: /Z0R0K.js
------------------------------------
Best of luck to you all! ~ VXAZ

[pire111]

proof the source code isn't malicious?

[VXAZ]

proof the source code isn't malicious?

I would never post a working JS JIT compiler exploit out to HF for free if there was a chance it could be reverse engineered and utilized. The source is merely a performance test for my obfuscator but I decided to post the performance test on HF as a challenge for reverse engineers to see if it can be deobfuscated (hence why I also requested that they include an estimated time it took them to deobfuscate it).

[pire111]

I would never post a working JS JIT compiler exploit out to you HF for free if there was a chance it could be reverse engineered and utilized the source is merely a performance test for my obfuscator but I decided to post the performance test on HF as a challenge for reverse engineers to see if it can be deobfuscated (hence why I also requested that they include an estimated time it took them to deobfuscate it).

you still didn't provide proof

[VXAZ]

you still didn't provide proof

if you don't believe me audit the HEAP in a virtualized environment or audit the FS I/O from your browser at runtime but something tells me you wont actually do that

[alexprivet888]

looks like a basic level noob trying to fish you XD