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
7 findings · run finished 2026-09-12 06:04Z · worst first
CriticalNewRoot account usedpart of case k/cbfca6f4bf85prod-acct · us-east-1 / payments-prod-cluster-0
‹generated-workload-0› +30dDisabling 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. Root account used on generated-workload-0 in us-east-1 (account 123456789012): first seen 0 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-001 · f/A4kqZHhQXj · e/123456789ABC e/89ABCDEFGHJK e/FGHJKLMNPQRS +1
CriticalNewAccess keys minted across users in a burstpart of case k/cbfca6f4bf851234567890120d
observed on synthetic accountsV-004 · f/5VA7vrDB4E · t/4b1c9e0a-1234-4abc-8def-0123456789ab
CriticalAMI shared publicly234567890123 · ap-southeast-1
‹generated-workload-64› +488dDisabling 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-64 in ap-southeast-1 (account 234567890123): first seen 88 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/A1JSYkfbQM · e/RSTUVWXYZabc e/YZabcdefghij e/fghijkmnopqr +2
CriticalAdministrator-equivalent AWS-managed policy on a service principalsandbox · us-west-2
‹generated-workload-56› +332dDisabling 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-56 in us-west-2 (account 345678901234): first seen 32 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/DSTWvQYDBY · e/HJKLMNPQRSTU e/QRSTUVWXYZab e/XYZabcdefghi +3
HighNewEC2 instance accepts IMDSv1 <on "prod">1234567890120d
observed on synthetic accountsV-013a · f/8qMQNSkNyV · e/8K95JNg2jDnJ
CriticalEC2 instance accepts IMDSv1part of case k/cbfca6f4bf85sandbox · eu-central-1‹generated-workload-8› +456d•Disabling 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. EC2 instance accepts IMDSv1 on generated-workload-8 in eu-central-1 (account 345678901234): first seen 56 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-013a · f/2dTniNd4qd · e/9ABCDEFGHJKL e/GHJKLMNPQRST e/PQRSTUVWXYZa +9
HighNewWarden could not read part of its scope1234567890120d
observed on synthetic accountsV-025 · f/CL26TbwQFY · no record cited