Server running AI attack platform CyberStrikeAI used stolen AWS credentials
- Vendor
- Amazon Web Services
From Sep 30 to Oct 16, a server running the AI attack platform CyberStrikeAI used stolen credentials for eight identities in four AWS accounts, Elastic says. It read secrets, EC2 user data and an encrypted SSM parameter, then sent an SSM command. Elastic calls the intrusion AI-assisted from the tool and the machine speed in the logs, but it can’t prove an AI agent made the decisions. It doesn’t know how the credentials were stolen.
The eight were five IAM users and three EC2 instance roles. The server first checked which credentials worked, calling GetCallerIdentity on four IAM users across three accounts within 51 minutes, three of them in the same second. One instance role then read a secret and sent 56 user data requests in 141 milliseconds. On Oct 2 another role read an encrypted SSM parameter and issued an SSM SendCommand 29 seconds later. CloudTrail doesn’t show what that command was or whether it succeeded.
After 14 quiet days the server came back on Oct 16 and checked credentials again, including a user in a fourth account. The three role sessions were named after EC2 instance IDs, so their credentials came from instance profiles. Elastic says using them from an outside address means they were taken from the instances, for example through SSRF or host compromise.
The activity set off 78 alerts across six rules, all medium or low severity, and 65 came on the first day. Elastic says they made sense only when grouped by source IP, and a short, fixed correlation window would have split the intrusion into unrelated alerts. It has added two high-severity detections, for bulk reads of user data and bulk GetCallerIdentity calls.
Internet scans showed the address serving a CyberStrikeAI web interface on port 8080 a day before the first alert. Two more addresses in the same range serve the same self-signed certificate but didn’t appear in this intrusion, and as of November none of the three serves the interface. Team Cymru earlier counted 21 addresses running the platform, all aimed at Fortinet devices, and Elastic says this is the first case it has seen against AWS.
- Vendor
- Amazon Web Services
What to do
8 steps
Indicators
IPs copy defanged. Use Copy raw for queries.
| Type | Value | Note |
|---|---|---|
| IP address | Source of all 78 alerts, a CyberStrikeAI server on port 8080 | |
| IP address | Serves the same CyberStrikeAI certificate, not seen in this intrusion | |
| IP address | Serves the same CyberStrikeAI certificate, not seen in this intrusion |
- IP addressSource of all 78 alerts, a CyberStrikeAI server on port 8080
- Network
- IP addressServes the same CyberStrikeAI certificate, not seen in this intrusion
- Network
- IP addressServes the same CyberStrikeAI certificate, not seen in this intrusion
- Network
Timeline
- Sep 30The server checks stolen credentials and reads secrets and EC2 user data, setting off 65 alerts.
- Oct 1–2It reads more secrets and an encrypted SSM parameter, then sends an SSM command.
- Oct 16It comes back after 14 days and checks credentials, including a user in a fourth account.
- Nov 13Elastic publishes its report.
Sources
- Elastic researchPrimary source elastic.co