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
CriticalNewRoot account used234567890123 · us-east-1
‹generated-workload-40› +8100dDisabling 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-40 in us-east-1 (account 234567890123): first seen 100 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/ArnVq4KxdQ · e/123456789ABC e/89ABCDEFGHJK e/FGHJKLMNPQRS +5
CriticalEC2 instance accepts IMDSv1prod-acct · eu-central-1 / payments-prod-cluster-0
‹generated-workload-48› +9156d•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-48 in eu-central-1 (account 123456789012): first seen 156 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/2MABPzB2Np · e/9ABCDEFGHJKL e/GHJKLMNPQRST e/PQRSTUVWXYZa +4