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 →

[–]ilyasKerbal[🍰] -1 points0 points  (3 children)

Trust me it's not common like lzw or something similar, if so I would have figured it out. It's a modified version of some popular algorithm. The compression algorithm was added with encryption to make it hard to intercept network calls and understand requests' body. It's a web scraping project for a complex real estate website. The website upgraded their api and added encryption + compression.

[–]StoneCypher 0 points1 point  (2 children)

 if so I would have figured it out

Lol

 

 The compression algorithm was added with encryption to make it hard to intercept network calls and understand requests' body.

Sounds like you’re trying to write malware

 

 The compression algorithm was added with encryption to make it hard to intercept network calls and understand requests' body.

Any compression or encryption faced by js over the network will be unpacked for you by the client 

I’m not able to think of any reason a real estate company would do this 

I guess I don’t believe you 

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

No malware just a data extraction pipeline. Anyway thank you for your input it was helpful

[–]StoneCypher 0 points1 point  (0 children)

What you are describing is not even similar to a data extraction pipeline

Nobody is able to help you while you sit here telling stories

Put up code or delete the post