Composio. The access path.
A broker holding agent credentials lost customer OAuth tokens for connected SaaS. A credential broker concentrates reach by design. That is the point, and that is the risk.
The record
Entry point. infrastructure monitoring tool, initial access to internal systems.
The identity in the middle. The product itself: customer OAuth tokens and API keys for connected SaaS accounts, held so agents can act on them, plus 5,241 Composio API keys from an auxiliary cache service and an internal GitHub token with production code access.
What was reached. connected SaaS accounts, about 0.3 percent of active connections, the largest group 5,001 GitHub connections.
A broker holding agent credentials lost customer OAuth tokens for connected SaaS.
The path, step by step.
Taken from the published reporting. Nothing here is reconstructed.
| Step | Role in the path | What the reporting records |
|---|---|---|
| infrastructure monitoring tool | Entry | initial access to internal systems |
| automated remediation and tool definitions | Step | escalation into the tool execution sandbox, with code execution there |
| credential store | Step | customer OAuth tokens and API keys for connected accounts |
| connected SaaS accounts | Reached | about 0.3 percent of active connections, the largest group 5,001 GitHub connections |
Where a breakpoint would have been
Blast radius at the store, not at the entry. Agent platforms exist to hold other people tokens, so the question is never whether someone gets in but how many connections one compromise reaches. Envelope encryption and per connection isolation are what turn a breach into a bounded one.
A breakpoint is the single change that closes a path with the least disruption. Read how that is chosen in the breakpoint page.
4 steps from entry to data.
Where this comes from.
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.
Questions, answered.
The two questions this record answers.
What was the entry point in the Composio incident?
The published path starts at infrastructure monitoring tool, initial access to internal systems.
What did it reach?
The last step in the published path is connected SaaS accounts, about 0.3 percent of active connections, the largest group 5,001 GitHub connections.
Other incidents.
Same database, different path shape.
See what your agents can reach. Before someone else does.
Book a demo and we walk through the access paths in an environment like yours.