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
3 findings · run finished 2026-09-12 06:04Z · worst first
MediumAMI shared publiclysandbox · ap-southeast-1
‹generated-workload-44› +5128dDisabling 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-44 in ap-southeast-1 (account 345678901234): first seen 128 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/5aaW9ER6hH · e/56789ABCDEFG e/CDEFGHJKLMNP e/KLMNPQRSTUVW +9
MediumAMI shared publiclyprod-acct · ap-southeast-1 / payments-prod-cluster-0‹generated-workload-84› +348dDisabling 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-84 in ap-southeast-1 (account 123456789012): first seen 48 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/5mr1sAbQ9K · e/56789ABCDEFG e/CDEFGHJKLMNP e/KLMNPQRSTUVW +4
MediumAMI shared publicly234567890123 · ap-southeast-1‹generated-workload-4› +728dDisabling 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-4 in ap-southeast-1 (account 234567890123): first seen 28 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/3BBJZUDogz · e/56789ABCDEFG e/CDEFGHJKLMNP e/KLMNPQRSTUVW +5