3 ms·
A colleague and I did something similar recently. We got similar spam mails in our work inboxes. Whipped up a little ruby script that spammed bum login data to
by beAbU 6y ago
A colleague and I did something similar recently.
We got similar spam mails in our work inboxes. Whipped up a little ruby script that spammed bum login data to the spammer's form url. We had our scripts running on a couple of Heroku instances and all.
At some stage we realized that the password field in the form accepted arbitrarily sized payloads. So we base64 encoded some 10MB file and sent that as the password. The thinking was if we could not DoS them, we can at least clog up their works with some real hefty payloads.
More can be seen here: https://github.com/dj-louw/spamscam https://github.com/dj-louw/spamscam
- Sebb767 6y agoWhile funny, real-looking fake login data might be more useful, as it's probably real easy to filter the few large requests. Unless, of course, you bring down the server and stop the whole operation (for a time). It would be quite interesting to do a study on both options using a honeypot-account (to detect whether the login could be extracted by the spammer).
- beAbU 6y agoSo the script we wrote created real email addresses and user names. The Ruby gem Faker (https://github.com/faker-ruby/faker https://github.com/faker-ruby/faker) takes care of that. But yeah you are probably right. 10MB passwords possibly made it too easy for the scammer to filter out the bum data. We did only make the 10MB change very late in our attack, so the scammer got 1000's of fake names and emails before we cranked up the mass of each individual request.