Hackers breach OpenAI using Claude tools, gaining access to employee accounts and the company's internal codebase — attackers initiated a 'harmless' pull request as proof of the hack
- ID
- 25970
- Status
- summarized
- Published
- 18 Sep 2026, 9:45 PM
- Fetched
- 18 Sep 2026, 11:12 PM
- Provider
- Tom's Hardware
- Category
- technology
- Original URL
- https://www.tomshardware.com/tech-industry/cyber-security/hackers-breach-openai-using-claude-tools-gaining-access-to-employee-accounts-and-the-companys-internal-codebase-initiating-a-harmless-pull-request-as-proof-of-the-hack
- Source URL
- https://www.tomshardware.com/feeds/all
Summary
- Score
- 7.5
- Created
- 18 Sep 2026, 11:12 PM
- Tags
- Audience
- developersai_agent_userssaas_founders
What happened
Hackers reportedly breached OpenAI by leveraging Claude tools, gaining access to employee accounts and OpenAI's internal codebase. As proof of the intrusion, the attackers submitted a 'harmless' pull request within the company's repositories.
Why it matters
If AI coding assistants and agent tools can be turned into an attack vector against the very company building them, any team shipping AI-agent workflows that touch code repos, credentials, or internal systems should scrutinize what permissions their agents have and whether agent-initiated PRs or commits are gated by human review and least-privilege access.
Discussion angle
What access scopes and review gates are you putting on AI agents that interact with your codebase — and does this incident change your threshold for trusting agent-initiated changes?