Observed incident

GitBook traces production access to forged staff sessions

Reported

Published here

What happened

GitBook says an attacker targeting a customer used an SSO flaw to impersonate staff, reached internal source repositories through an integration and obtained production secrets. Customer tokens, documents and questions sent to GitBook Assistant were accessible.

Parties and reporting

AI tools and systems: Unidentified AI-assisted automation (GitBook assessment), GitBook Assistant, GitBook SSO and Git Sync, Cloudflare API key

Outcome

GitBook reported about 16 hours of downtime, closed the access paths, revoked API tokens and rotated its infrastructure and managed customer secrets. It could not determine what actions were taken in connected customer repositories.

Operating lesson

Replace revoked API tokens, rotate third-party integration secrets, regenerate custom-backend signing keys where applicable, and audit repository access during the incident.

Evidence and limits

November 2 was the intrusion, November 3 the first public notice and November 4 the postmortem. GitBook inferred AI use from attack speed and precision. No model was identified. GitBook treated accessible customer data as exposed without establishing that all of it was copied.

Sources