Case gitbook-ai-agent-attackAI-assisted malwareWorldwide
GitBook discloses AI agent attack exposing some infrastructure credentials
GitBook disclosed that on 2 Nov 2026 an attacker, described by the company as using AI agents in a targeted attack, gained unauthorized access to parts of its infrastructure and some infrastructure credentials. The company reported no evidence that customer content was altered and urged users to rotate their keys. The attacker's identity and exactly how the AI agents were used were not disclosed.
HighAttack using AIStatus: contained; service restored 3 Nov 2026Verified case file
Open in the interactive mapCite this case
- Reported
- Nov 3, 2026
- Location
- Worldwide
- Target
- GitBook infrastructure credentials
- Severity
- High
- Verification
- Reported by credible press or researchers
- Triggered by
- Unknown
- Actor type
- Unknown
- Sector
- Technology & AI vendors
- Reported loss
- None reported
- CVE
- None
What happened
GitBook disclosed that on 2 Nov 2026 an attacker, described by the company as using AI agents in a targeted attack, gained unauthorized access to parts of its infrastructure and some infrastructure credentials. The company reported no evidence that customer content was altered and urged users to rotate their keys. The attacker's identity and exactly how the AI agents were used were not disclosed.
Impact: Integration tokens, Git Sync keys, API tokens and questions visitors sent to GitBook Assistant may have been exposed; no tampering with customer content was found. Published docs sites and the app were disrupted, and PancakeSwap temporarily took its GitBook-hosted docs offline.
Who triggered it
Actor: Unknown
Attribution: Unattributed; GitBook describes the attack as carried out by an AI agent.
Motive: Unknown
How it happened
Attack vector: AI agent-driven intrusion; exact method Unknown.
Root cause: Unknown
Timeline
- Reported by BlockBeats
Response
GitBook revoked all personal API tokens and replaced credentials, restored service on 3 Nov, and advised users to rotate GitBook and third-party API tokens and keys and re-authenticate the GitBook MCP server.
Current status: contained; service restored 3 Nov 2026
Research warnings this case matches
- Seen in real incidents AI makes cyberattacks easier, faster and larger · CAIS
- Seen in real incidents Criminals and state hackers use AI in cyberattacks · International AI Safety Report
- Seen in real incidents Malicious actors and misuse · MIT AI Risk Repository
Compared with published AI risk research from several institutes on the Research vs reality page.
Sources (open in a new tab)
- BlockBeats news.google.com
- Decrypt decrypt.co
- GitBook status (Pulsetic) pulsetic.com
Cite this case
GitBook discloses AI agent attack exposing some infrastructure credentials. AI Threat Watch, case gitbook-ai-agent-attack, Nov 3, 2026. https://aithreat.io/cases/gitbook-ai-agent-attack/
Permanent link: https://aithreat.io/cases/gitbook-ai-agent-attack/
Related cases
The same type of incident, most recent first.