3 ms·
Interesting tweet here[0] saying the site was used to phish credentials since late February this year. Also, who was hosting these guys? I remember in early 20
by skilled 5y ago
Interesting tweet here[0] saying the site was used to phish credentials since late February this year.
Also, who was hosting these guys? I remember in early 2000s (back when milw0rm was a thing) - a lot of sites like this struggled to stay online because nobody wanted to host them.
Anyways, that's a pretty stupid way to go out. And, not just because he is at fault or whatever, it sounds like they turned that site into a capitalist enterprise and that's going to hurt more than the fact that he engaged in illegal activity in the first place.
[0]: https://twitter.com/NatSecGeek/status/1513875386395987968 https://twitter.com/NatSecGeek/status/1513875386395987968
- twelventy 5y ago> who was hosting these guys? Epik?
- toyg 5y agoI reckon the move to automated deployments in the cloud, must have made it relatively easy to cycle through accounts. Any mid-size hosting companies these days has an api, so you write scripts to deploy your (pretty simple) services on Host A with account A, and when the ban happens, move to Host B with account A, then back to Host A with account B, then host B with account B, then host A with account C, etc etc.