{"schema_version":"0.10.0","id":"LR-2026-0827","record_version":1,"title":"GitBook infrastructure credentials compromised in AI-agent-assisted intrusion","verification":{"human_verified":false,"method":"automated_gate","auto_verified":true,"score":50.3,"score_breakdown":{"source_authority":12.1,"independent_corroboration":7.0,"implicated_party_confirmed":0.0,"citation_integrity":14.0,"specificity":3.0,"completeness":6.72,"unhedged_language":5.0},"checks":{"schema_valid":true,"every_field_cited":true,"quotes_verbatim":true,"source_fetched":true,"distinct_incident":true,"dates_plausible":true,"sources_agree":true,"source_describes_incident":true,"severe_backed_by_source":true,"record_integrity":true,"eligible":true,"about_this_case":true},"gate_version":"gate-2026-10-18.7","cross_check_model":null,"cross_check_agreement":null,"duplicate_of":null,"verified_by":null,"verified_at":"2026-11-04","extraction_run_id":null,"evidence_level":{"level":"preliminary","reason":"1 report: crypto.news · subject to change","original_document":null,"reports_total":1,"reports_independent":1,"reports_derivative":0,"developing":true,"disputed":false,"rules_version":"evidence-2026-10-29.1","computed_at":"2026-11-04","history":[{"date":"2026-11-04","from_level":null,"to_level":"preliminary","reason":"1 report: crypto.news · subject to change"}]},"sources_hash":"8345b9365542545c1684d5adce6121a470dac3e3aeba28066baf360de5825aba"},"system":{"model_name":null,"model_version":null,"developer":"unknown","harness":null,"tools_granted":[],"permissions_scope":null,"autonomy_level":"unknown","guardrails_present":[],"deployment_context":"production","tier":null,"lifecycle_stage":null,"integration_type":null,"intended_use":null,"safeguard_state":null,"production_intended":null},"event":{"date_occurred":"2026-11-02","date_disclosed":"2026-11-03","incident_class":"security_compromise","failure_class":"credential_misuse","agent_involved":true,"secondary_failure_classes":[],"trigger":"unknown","duration":null,"detection_method":"automated_monitor","summary":"GitBook, a documentation provider, reported that an attacker gained unauthorized access to some of its infrastructure credentials at 7 p.m. CET on Nov. 2, in what it described as a sophisticated, highly targeted attack using AI agents. GitBook said it detected the attack immediately and moved to contain it, taking the application and documentation sites requiring authentication offline while securing its infrastructure. It blocked the attacker, closed the vulnerabilities involved, and replaced every credential and secret across its infrastructure, invalidating customer API tokens. Its investigation identified four categories of potentially accessed information: integration tokens, Git Sync secrets, API tokens, and questions submitted by documentation visitors to GitBook Assistant. Customers were told to rotate GitBook and third-party API tokens and secrets and to reauthenticate connections to the GitBook MCP server. By its Nov. 3 update, the application, API and published documentation were available again.","tags":["credential-theft","ai-agents","data-exfiltration","cyberattack","api-tokens"],"date_detected":"2026-11-02","near_miss":null,"root_cause":null,"root_cause_detail":null,"failure_class_detail":"The document states the attacker gained unauthorized access to infrastructure credentials in an attack it describes as using AI agents; it does not describe the agents' specific actions, so the mechanism is classified from the stated credential access (grade D).","responsible_party":"third_party","adversarial_actor":"external_attacker","input_provenance":null,"time_to_contain":null,"operations_paused":"The application and documentation sites requiring authentication were taken offline; by the Nov. 3 update at 4:21 p.m. CET the application, API and published documentation were available again, with restoration continuing on some services.","remediation":"GitBook blocked the attacker, closed the vulnerabilities involved, replaced every credential and secret across its infrastructure, invalidated customer API tokens, and told customers to rotate GitBook and third-party API tokens and secrets and reauthenticate connections to the GitBook MCP server; it said it was introducing additional security measures.","precursor_events":null},"impact":{"direct_loss_usd":null,"remediation_hours":null,"records_exposed":null,"third_parties_affected_count":null,"severity":"major","severity_because":"Major: a live production compromise described as a platform-wide issue affecting a number of customers, with credentials and visitor questions potentially accessed.","harm_class":["third_party_security","privacy","operational"],"affected_description":"GitBook customers and documentation visitors; potentially accessed data includes integration tokens, Git Sync secrets, API tokens, and visitors' Assistant questions","protected_class_involved":null,"data_categories_exposed":["credentials"],"loss_range_usd":null,"reversibility":null,"downstream_exposure_count":null},"evidence":{"sources":[{"url":"https://crypto.news/gitbook-ai-cyberattack-api-tokens-secrets/","publisher":"Crypto News","date":"2026-11-03","type":"press","title":"GitBook urges token resets after AI-powered cyberattack","archived_url":null,"attachment":"first_report","independence":"independent"}],"per_field_confidence":{"system.developer":"D","system.autonomy_level":"D","system.deployment_context":"C","event.date_occurred":"C","event.date_disclosed":"C","event.failure_class":"C","event.trigger":"D","event.detection_method":"C","event.summary":"C","event.tags":"C","event.date_detected":"C","event.responsible_party":"C","event.adversarial_actor":"C","event.operations_paused":"C","event.remediation":"C","event.incident_class":"C","event.agent_involved":"C","event.failure_class_detail":"C","impact.severity":"C","impact.harm_class":"C","impact.affected_description":"C","impact.data_categories_exposed":"C","impact.severity_because":"C","context.industry":"C","context.country":"D","context.denominator_available":"D"},"field_citations":{"system.deployment_context":[{"source_index":0,"quote":"GitBook has urged customers to replace API tokens and integration secrets after an attack involving AI agents compromised infrastructure credentials and potentially exposed customer data."}],"event.date_occurred":[{"source_index":0,"quote":"According to GitBook’s incident notice, the attacker gained unauthorized access to some infrastructure credentials at 7 p.m. CET on Nov. 2, equivalent to 6 p.m. UTC or 1 p.m. U.S. Eastern time."}],"event.date_disclosed":[{"source_index":0,"quote":"By its Nov. 3 update at 4:21 p.m. CET, the application, API and published documentation were available again, although restoration work continued on some services."}],"event.failure_class":[{"source_index":0,"quote":"According to GitBook’s incident notice, the attacker gained unauthorized access to some infrastructure credentials at 7 p.m. CET on Nov. 2, equivalent to 6 p.m. UTC or 1 p.m. U.S. Eastern time."}],"event.detection_method":[{"source_index":0,"quote":"The documentation provider said it detected the attack immediately and moved to contain it."}],"event.summary":[{"source_index":0,"quote":"According to GitBook’s incident notice, the attacker gained unauthorized access to some infrastructure credentials at 7 p.m. CET on Nov. 2, equivalent to 6 p.m. UTC or 1 p.m. U.S. Eastern time."},{"source_index":0,"quote":"The documentation provider said it detected the attack immediately and moved to contain it."},{"source_index":0,"quote":"Describing the intrusion as a sophisticated, highly targeted attack using AI agents, GitBook said it blocked the attacker, closed the vulnerabilities involved, and replaced every credential and secret across its infrastructure."},{"source_index":0,"quote":"Its investigation identified four categories of potentially accessed information: integration tokens, Git Sync secrets, API tokens, and questions submitted by documentation visitors to GitBook Assistant."},{"source_index":0,"quote":"Customers have been told to rotate existing GitBook API tokens, with the company confirming that all personal API tokens were revoked during the incident."},{"source_index":0,"quote":"By its Nov. 3 update at 4:21 p.m. CET, the application, API and published documentation were available again, although restoration work continued on some services."}],"event.tags":[{"source_index":0,"quote":"GitBook has urged customers to replace API tokens and integration secrets after an attack involving AI agents compromised infrastructure credentials and potentially exposed customer data."},{"source_index":0,"quote":"Describing the intrusion as a sophisticated, highly targeted attack using AI agents, GitBook said it blocked the attacker, closed the vulnerabilities involved, and replaced every credential and secret across its infrastructure."},{"source_index":0,"quote":"Its investigation identified four categories of potentially accessed information: integration tokens, Git Sync secrets, API tokens, and questions submitted by documentation visitors to GitBook Assistant."}],"event.date_detected":[{"source_index":0,"quote":"The documentation provider said it detected the attack immediately and moved to contain it."}],"event.responsible_party":[{"source_index":0,"quote":"Describing the intrusion as a sophisticated, highly targeted attack using AI agents, GitBook said it blocked the attacker, closed the vulnerabilities involved, and replaced every credential and secret across its infrastructure."}],"event.adversarial_actor":[{"source_index":0,"quote":"According to GitBook’s incident notice, the attacker gained unauthorized access to some infrastructure credentials at 7 p.m. CET on Nov. 2, equivalent to 6 p.m. UTC or 1 p.m. U.S. Eastern time."}],"event.operations_paused":[{"source_index":0,"quote":"Its response included taking the application and documentation sites requiring authentication offline while securing its infrastructure."},{"source_index":0,"quote":"By its Nov. 3 update at 4:21 p.m. CET, the application, API and published documentation were available again, although restoration work continued on some services."}],"event.remediation":[{"source_index":0,"quote":"Describing the intrusion as a sophisticated, highly targeted attack using AI agents, GitBook said it blocked the attacker, closed the vulnerabilities involved, and replaced every credential and secret across its infrastructure."},{"source_index":0,"quote":"Customers have been told to rotate existing GitBook API tokens, with the company confirming that all personal API tokens were revoked during the incident."},{"source_index":0,"quote":"Users of the GitBook MCP server must reauthenticate their connection."},{"source_index":0,"quote":"GitBook said it was monitoring for further attacks and introducing additional security measures."}],"event.incident_class":[{"source_index":0,"quote":"GitBook has urged customers to replace API tokens and integration secrets after an attack involving AI agents compromised infrastructure credentials and potentially exposed customer data."},{"source_index":0,"quote":"Describing the intrusion as a sophisticated, highly targeted attack using AI agents, GitBook said it blocked the attacker, closed the vulnerabilities involved, and replaced every credential and secret across its infrastructure."}],"event.agent_involved":[{"source_index":0,"quote":"Describing the intrusion as a sophisticated, highly targeted attack using AI agents, GitBook said it blocked the attacker, closed the vulnerabilities involved, and replaced every credential and secret across its infrastructure."}],"event.failure_class_detail":[{"source_index":0,"quote":"According to GitBook’s incident notice, the attacker gained unauthorized access to some infrastructure credentials at 7 p.m. CET on Nov. 2, equivalent to 6 p.m. UTC or 1 p.m. U.S. Eastern time."}],"impact.severity":[{"source_index":0,"quote":"GitBook described the incident as a platform-wide issue affecting a number of customers."},{"source_index":0,"quote":"Its investigation identified four categories of potentially accessed information: integration tokens, Git Sync secrets, API tokens, and questions submitted by documentation visitors to GitBook Assistant."}],"impact.harm_class":[{"source_index":0,"quote":"Its investigation identified four categories of potentially accessed information: integration tokens, Git Sync secrets, API tokens, and questions submitted by documentation visitors to GitBook Assistant."},{"source_index":0,"quote":"Its response included taking the application and documentation sites requiring authentication offline while securing its infrastructure."}],"impact.affected_description":[{"source_index":0,"quote":"Its investigation identified four categories of potentially accessed information: integration tokens, Git Sync secrets, API tokens, and questions submitted by documentation visitors to GitBook Assistant."}],"impact.data_categories_exposed":[{"source_index":0,"quote":"Its investigation identified four categories of potentially accessed information: integration tokens, Git Sync secrets, API tokens, and questions submitted by documentation visitors to GitBook Assistant."}],"impact.severity_because":[{"source_index":0,"quote":"GitBook described the incident as a platform-wide issue affecting a number of customers."}],"context.industry":[{"source_index":0,"quote":"The documentation provider said it detected the attack immediately and moved to contain it."}]},"notes_on_gaps":"The document does not name the AI agents, their developer, the tools they were granted, or how they were used in the intrusion; it only says the attack used AI agents. No customer count, record volume, or monetary loss is stated. The detection method is coded automated_monitor only because GitBook says it 'detected the attack immediately'; the mechanism of detection is not specified. The trigger is left unknown because no cause is named. Root cause is unknown: the document says vulnerabilities were closed but does not identify what failed. Country of the operator is not stated. The separate Trade.xyz documentation incident on Nov. 2 is described as unauthorized activity on GitBook pages with no stated AI involvement and no established link to the GitBook intrusion, so it is not recorded as a separate incident here. The Oct. 30 Google Threat Intelligence/Mandiant research report is a research report with no concrete dated incident and is not recorded. Extractor proposed values without quotes; dropped: ['context.country', 'context.denominator_available', 'event.root_cause', 'event.trigger', 'impact.reversibility', 'system.autonomy_level', 'system.developer']. Single secondary source; corroborate before upgrading any field to B. [2026-11-04: evidence level set: Preliminary (1 report: crypto.news · subject to change)]"},"context":{"industry":"Software Publishers","org_size_band":null,"country":"unknown","denominator_available":false,"denominator":null,"related_incident_ids":[],"systemic_exposure":null,"shared_model_id":null,"upstream_incident_id":null,"incident_evidence":null,"regulatory":null,"coverage":null}}