SecOraLens
HighCVE

56 AWS API calls in 141 milliseconds: Inside an AI-run intrusion

Elastic Security Labs·Source published ·1 min read

What happened?

One server read 56 EC2 user data scripts in 141 milliseconds. Then it went quiet for 14 days and came back. That gap did more damage than the burst, because fixed correlation windows cannot span two weeks. Between September 30 and October 16, 2026, a CyberStrikeAI server worked through stolen AWS credentials in a familiar sequence: validate identities, harvest secrets from Secrets Manager, pull EC2 user data, decrypt an SSM parameter, send a remote command. Every one of those is a call a legitimate role makes every day. Nothing in CloudTrail looked urgent at the time.

Key details

  • One CyberStrikeAI server used eight stolen AWS identities across four accounts over 16 days.
  • The attacker revalidated credentials and issued an SSM SendCommand 29 seconds after reading an encrypted SSM parameter.
  • Six Elastic detection rules fired, but each produced only medium or low severity alerts until correlated by source IP.
  • Three IPs in the 43.240.29.x range serve CyberStrikeAI with identical self-signed certificates.

Summarised by SecOraLens from Elastic Security Labs. Always read the original source before acting. How SecOraLens verifies advisories.

What to do next

For CISOs and SOC leads

Brief your board. Brief your team.

Executive risk briefs for governance, technical kill-chains for the SOC — delivered as advisories publish. Critical alerts within 1 hour. No spam, unsubscribe anytime.