Guide · Breach of the week
STOP ignoring a vendor's “reset your keys” notice
If a company you rely on says an attacker got into its systems and tells you to rotate your keys, do it now. This week GitBook, a documentation platform, did exactly that. The keys that connect your other tools to a vendor are yours to replace, and the vendor can’t do it for you.
In under a minute:
- Use GitBook, or have a help center or docs site on it? Create new GitBook API tokens. GitBook revoked all personal API tokens during the incident.
- Replace every key you gave other tools to connect to GitBook, and any secrets in published integrations. Create the new one, update the tool, then delete the old one.
- Not sure? Ask whoever manages your website or docs today.
Know which vendors hold your keys before one is breached. The Small Business Security Essentials Toolkit ($79) includes a Vendor Security Check, an Asset & Admin Inventory to list where each tool and key lives, and an incident response pack for the day a vendor tells you to act.
What happened
According to GitBook’s status page, an attacker gained unauthorized access to some of its infrastructure credentials at 19:00 CET on November 2, 2026. GitBook says it detected the attack immediately, blocked the attacker, replaced every credential and secret across its infrastructure, and invalidated every customer’s API tokens. It took the app and authenticated docs sites offline, kept published public content live from cache, and brought services back on November 3. On November 4 it marked the incident resolved and published a full incident postmortem (Security incident | November 2026). The postmortem says an SSO flaw let the attacker create staff sessions, reach production secrets, and access customer API tokens, integration tokens/secrets, and related data; GitBook found no evidence other customers’ content was modified. Customers must still create new API tokens and rotate third-party/integration secrets per GitBook’s checklist. Earlier customer notices also described the attack as sophisticated, highly targeted, and using AI agents (Decrypt).
GitBook says the attacker may have accessed integration tokens, Git Sync secrets, API tokens, and questions that site visitors asked GitBook Assistant. It says it has found no evidence that any content in GitBook was modified.
What to do now
GitBook’s own list for customers, in plain terms:
- Rotate any existing GitBook API tokens. Personal API tokens were all revoked, so create new ones where something still needs them.
- Rotate any third-party tokens or secrets you use to connect other tools to GitBook.
- If you use published integrations that carry secrets, rotate those secrets.
- If you use the GitBook MCP server, re-authenticate it.
- Ask your GitBook organization’s admin to help if you can’t do this yourself.
One note from GitBook: because of a GitHub outage unrelated to this incident, Git Sync was still affected on November 4. Check GitBook’s status page and its postmortem for anything still outstanding.
How to replace a key without breaking things
This is general good practice, not GitBook’s wording:
- Create the new key in the service that issues it.
- Put it into the tool that uses it and confirm the connection works.
- Delete or revoke the old key. A key you leave active can still be used by anyone who copied it.
- Write down where each key lives and who owns it, so the next notice takes minutes.
If you run a team
- Ask your web person or developer today whether you publish docs, a help center or a knowledge base on GitBook, and which keys connect to it.
- Treat “reset your keys” notices from any vendor as same-day work, not something for the inbox pile. See contractor access without shared logins for tracking who holds access.
Bottom line
When a vendor is breached, the vendor fixes its side and you fix yours. The keys you handed to other tools are the part only you can replace.
Prefer video? Watch the under-a-minute version on YouTube: STOP Ignoring a Vendor's "Reset Your Keys" Notice.
Free next step: Get the Small Business Cybersecurity Checklist — download it now, or sign up there to get it by email and hear about new guides.