GitBook says AI-agent attack compromised credentials, revokes all customer API tokens

GitBook says AI-agent attack compromised credentials, revokes all customer API tokens

BACOOR NEWS1 min read

GitBook says an attack using AI agents compromised infrastructure credentials on 2 November. It revoked all customer API tokens and told users to rotate connected secrets.

In brief

  • GitBook says an attack using AI agents compromised infrastructure credentials on 2 November.
  • The platform revoked all customer API tokens and replaced its own infrastructure credentials and secrets.
  • Users are told to rotate GitBook and third-party tokens and re-authenticate the GitBook MCP server.

What happened

GitBook is a platform teams use to create and publish documentation and knowledge bases.

According to Coin Bureau, an attack using AI agents compromised infrastructure credentials on 2 November.

The attacker may have accessed integration tokens, Git Sync secrets, API tokens and questions visitors asked GitBook Assistant, Coin Bureau reported.

GitBook revoked all customer API tokens and replaced its infrastructure credentials and secrets.

The app, API and published docs are back online, though some services remain degraded.

GitBook found no evidence that content was modified, according to the same report.

Separately, Solid Intel reported that Trade.xyz's GitBook documentation was compromised and warned users not to click links, as reported in our market pulse.

Why it matters

Documentation platforms sit inside the toolchain of crypto teams.

They hold integration tokens, sync secrets and API keys that connect to code repositories and other services.

A breach there is a supply-chain risk: stolen secrets can be reused against the systems they unlock.

The warning lands in a week of crypto security incidents, including the Binance hack that reached internal wallets.

What to watch

GitBook users are told to rotate GitBook and connected third-party tokens and secrets.

They should also re-authenticate the GitBook MCP server, according to Coin Bureau.

Teams that publish docs through GitBook should check which integrations and Git Sync connections used the revoked tokens.

The degraded services are the next signal of how far the cleanup has gone.

Sources

  1. Coin Bureau - Coin Bureau alert on GitBook credential breachReport

Related articles

More in Security

Nothing on BACOOR NEWS is financial advice.

BACOOR NEWS is developed by BACOOR's Japan team and provides news, editorial content, and market data for informational purposes only. Nothing published constitutes financial or investment advice, or an offer, solicitation, or recommendation to buy, sell, or hold any financial product or digital asset. Coverage of any token, trading pair, company, protocol, or project does not imply endorsement or promotion. Digital asset markets involve significant risks. Always conduct your own research (DYOR) and review our Disclaimer before making investment decisions.

AI Content Transparency: Market Pulse summaries are automatically generated using artificial intelligence (AI) based on third-party information and market data. News articles and other editorial content may also be drafted, edited, or otherwise prepared with AI assistance. BACOOR does not independently verify all third-party information before publication. AI-generated or AI-assisted content may contain errors, omissions, or outdated information. Readers are encouraged to verify important claims against the original sources. BACOOR may correct, update, or remove inaccurate content when identified.

Product Promotions: BACOOR NEWS may display clearly identified promotional content about BACOOR's own products and services where permitted by applicable law. Crypto-related promotional banners are not displayed on the Vietnamese-language edition or to visitors in Vietnam. Such promotional material is separate from editorial news and market data.

Data and Information Sources: alternative.me, Bankless, Arkham, Binance, Bitget, Bybit, Coinbase, Coin Bureau, DefiLlama, DEX Screener, ExchangeRate-API, Farside Investors, U.S. Bureau of Labor Statistics, U.S. Bureau of Economic Analysis, Federal Reserve, Bank of Japan, Cabinet Office of Japan, Gate, Hyperliquid, Lookonchain, MEXC, OKX, PatternPlus, Forex Factory, SEC EDGAR, Solid Intel, SoSoValue, Trust Wallet assets, Wikidata, CoinGecko, GeckoTerminal, e-Stat, FRED (Federal Reserve Bank of St. Louis), Japan Customs (Ministry of Finance), Wikimedia Commons, the official blogs and GitHub releases of the projects we cover, and Watcher Guru. External information may be delayed, inaccurate, or incomplete. Source attribution does not imply affiliation or endorsement.

This service uses the API function of e-Stat (Portal Site of Official Statistics of Japan), but its content is not guaranteed by the Japanese government.

Build version: 11403dc · 2026-11-20 06:52 GMT+7