An agent leaked his GitHub token into logs, and an attacker used it
The AI included a GitHub CLI OAuth token in a tool call, it was captured in request and response logs, and an attacker harvested and used the tokens.
This one went wrong. Read what happened so you don’t hit the same problem.
How it works
- The agent includes a code-host OAuth token in a tool call
- It is captured in request and response logs
- An attacker harvests and uses the tokens
Why it’s worth knowing
Logs are a publication nobody reads until the wrong person does.
Where it’s from
Summarized from a public post on news.ycombinator.com. See the original ↗