The article linked to a fork of the deleted github repo: https://github.com/eggdroid/eggseed3/blob/8b92ec0f8b251c9fe91cd64c86803f5b1cf0e3d3/jscript/iotaseed.js#

The article linked to a fork of the deleted github repo: https://github.com/eggdroid/eggseed3/blob/8b92ec0f8b251c9fe91cd64c86803f5b1cf0e3d3/jscript/iotaseed.js#L203 https://github.com/eggdroid/eggseed3/blob/8b92ec0f8b251c9fe9... But that piece of code should've triggered red flags even if the hacker didn't add a payload to overwrite Math.seedrandom to always use the same seed. The fact that https://github.com/davidbau/seedrandom https://github.com/davidbau/seedrandom isn't cryptographically secure should've been enough to turn you away and warn other. And if you read it a bit more you'll notice that it is mostly junk code (unused variables like visitedHash, newindex). Props to the hacker for the method acting. From the commit log https://github.com/eggdroid/eggseed3/commits/master https://github.com/eggdroid/eggseed3/commits/master I would not have suspect any malicious intent and just attribute it to incompetence (which might've worked better underhanded-c-contest style instead of using an explicit backdoor).