Attack in progressA leaked CI key of ‹ci-deploy-bot› is being used to break in: 6 accounts and machines created.Open the case
Findings
2 findings · run finished 2026-09-12 06:04Z · worst first
CriticalAMI shared publiclyprod-acct · ap-southeast-1 / payments-prod-cluster-0
‹generated-workload-24› +6168dDisabling the key makes the existing log files unreadable now. A deletion that runs its course makes them unreadable permanently, without a single log file being touched. AMI shared publicly on generated-workload-24 in ap-southeast-1 (account 123456789012): first seen 168 days ago and still present on the run that wrote this board; the weak set grew from 0 to 2 between the two runs, and none of the new members is covered by an allowlist entry.V-008 · f/CriCJcMezw · e/RSTUVWXYZabc e/YZabcdefghij e/fghijkmnopqr +7
CriticalAdministrator-equivalent AWS-managed policy on a service principalpart of case k/cbfca6f4bf85234567890123 · us-west-2
‹generated-workload-16› +5112dDisabling the key makes the existing log files unreadable now. A deletion that runs its course makes them unreadable permanently, without a single log file being touched. Administrator-equivalent AWS-managed policy on a service principal on generated-workload-16 in us-west-2 (account 234567890123): first seen 112 days ago and still present on the run that wrote this board; the weak set grew from 0 to 2 between the two runs, and none of the new members is covered by an allowlist entry.V-010 · f/5zDhYAh8zQ · e/HJKLMNPQRSTU e/QRSTUVWXYZab e/XYZabcdefghi +8