Hacker News new | past | comments | ask | show | jobs | submit login

1. It may not be their bucket. Getting someone's credentials and uploading to S3 means the wrong party would be assigned blame/responsibility.

2. It may be their bucket, but with false credentials. Stolen CC and faked contact information.




Right, but if amazon disables the bucket then don’t they lose contact with all the infected hosts? And anyway, I can’t imagine expecting a recurring charge like an AWS account to last too long on a stolen CC.

Along with the apparent lack of any actual payload, it seems to point to this being some kind of proof of concept.


Bad guys have figured out there are tons of 1-year promo offers for AWS and hosting a single file stays well within the free tier. They toss a stolen card on the account to verify it, which honestly most people won't question a $1 charge then refund from Amazon.

They also had a backup hosted on Akamai.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: