Attack in progressA leaked CI key of ‹ci-deploy-bot› is being used to break in: 6 accounts and machines created.Open the case
EC2 instance accepts IMDSv1 <on "prod">
Highnew- Rule
V-013a- Account
- 123456789012
- Where
- account-wide
- First seen
- 2026-09-08
- Last seen
- 2026-09-10 (0 days)
- Verdict
- not rated
What Firekeeper saw
observed on synthetic accounts
Resources
No resource is named on this finding.
Evidence
e/8K95JNg2jDnJ
Guidance
This rule has no written guidance yet.
Across the last 30 runs
| From | To | Runs | State |
|---|---|---|---|
| 2026-09-12 | 2026-09-12 | 1 | new |
| 2026-08-14 | 2026-09-11 | 29 | no board input for that run |
Decisions on this finding
D-01J9Q700000000000000000000Accepted risk on one finding:V-013af/8qMQNSkNyV, up to High
Active · signed by alice@example.com · expires 2026-10-12 (in 30 days)
“IMDSv1 stays until the agent upgrade lands”
Active, but not holding this finding this run: either it was signed or approved after the run that wrote this board and counts from the next run, or the finding changed since it was signed.
Not a problem?
Signing one of these quiets this finding. Nothing changes until you sign with your passkey, and it ends on its own date unless someone renews it.