←back to thread

391 points kinj28 | 2 comments | | HN request time: 0.693s | source

Could there be any link between the two events?

Here is what happened:

Some 600 instances were spawned within 3 hours before AWS flagged it off and sent us a health event. There were numerous domains verified and we could see SES quota increase request was made.

We are still investigating the vulnerability at our end. our initial suspect list has 2 suspects. api key or console access where MFA wasn’t enabled.

1. brador ◴[] No.45660803[source]
Lot of keys and passwords being panic entered on insecure laptops yesterday.

Do not discount the possibility of regular malware.

replies(1): >>45662444 #
2. tylergetsay ◴[] No.45662444[source]
Or the keys were long compromised and yesterday someone opened permissions on them in order to mitigate