Three of six disclosed incidents were access problems, not alignment problems. Intent varied across the six incidents. What the agents could reach did not.
Entry point. agent-run, evaluation or production, the question is the same.
The identity in the middle. A leaked API key belonging to a third party, found by the agent on public GitHub.
What was reached. leaked-api-key, credential belonging to a third party.
Three of six disclosed incidents were access problems, not alignment problems.
Taken from the published reporting. Nothing here is reconstructed.
| Step | Role in the path | What the reporting records |
|---|---|---|
| agent-run | Entry | evaluation or production, the question is the same |
| open-egress | Step | outbound HTTP with no allowlist |
| public-github | Step | search for exposed secrets |
| leaked-api-key | Reached | credential belonging to a third party |
Outbound egress from the agent run. With no allowlist, searching public GitHub and then using what it finds is a single uninterrupted motion.
A breakpoint is the single change that closes a path with the least disruption. Read how that is chosen in the breakpoint page. The full narrative is in the teardown.
4 steps from entry to data.
Every field on this page is taken from the published reporting below. The breakpoint assessment is Elmoz reading that path, not a statement about what the affected organisation did.
The two questions this record answers.
The published path starts at agent-run, evaluation or production, the question is the same.
The last step in the published path is leaked-api-key, credential belonging to a third party.
Same database, different path shape.
Book a demo and we walk through the access paths in an environment like yours.