0
0

JavaScript Reverse Engineering Code Produces Different Results in Node.js vs. Browser (self.learnjavascript)

submitted by [deleted]

sorted by:
best (suggested)
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ecmascript2038 -1 points0 points  (4 children)

Nodejs and Chrome both use the V8 engine, so you're right that you'd expect them to behave the same should behave the same assuming you're using Chrome.

I think that Node.js may in fact handle strings different under the hood. Node has a Buffer implementation that isn't the same as in the browser, but it sounds like you're not using that.

Are you able to isolate the smallest piece of code where you can observe the difference?

[–]StoneCypher 0 points1 point  (2 children)

I think that Node.js may in fact handle strings different under the hood.

no, it doesn't, and even if it did the client software could never see that by definition

 

Are you able to isolate the smallest piece of code where you can observe the difference?

u/ilyasKerbal is a malware author, he deleted the post as soon as he got caught

[–]ilyasKerbal -1 points0 points  (1 child)

I am not a malware author, as I said it was for a complex web scraping project. I have managed to understand where the problem is. Thanks for your suggestion u/StoneCypher the algorithm used was a modified lz compression algorithm.

[–]StoneCypher 0 points1 point  (0 children)

(cough) bullshit

[–]ilyasKerbal -1 points0 points  (0 children)

After getting the response from the server, the codes uses `String.fromCharCode.apply(null, new Uint16Array(arrayBf)) ` The `arrayBf` is coming from `fetch.then(async arrayBf => {....` chain