Answers · Notion

Pasted a key into Notion AI? What the Fireworks incident means

If Notion didn't contact you: nothing. Its advisory (updated Nov 10): "If you haven't heard from us, we haven't identified your workspace as affected, and no action is needed right now."

If Notion did contact you: treat the transcripts as exposed, and rotate any credential you pasted into Notion AI. Notion: "If those with affected workspaces have pasted sensitive information, passwords, API keys, or other credentials into Notion AI during the timeframe of the incident, rotate them." This wasn't a breach of Notion's systems; it came through Fireworks AI, which Notion used for AI inference.

What happened, per Notion and Fireworks

For most affected workspaces the chats were "unattributable": not labeled with who wrote them or which workspace they came from, and without tool call results. Notion says no other Notion features were affected. It has disabled Insights and no longer serves open-weight models through Fireworks. Its investigation is ongoing.

  • Oct 23–24 (Fireworks). A "third-party cloud provider that hosted Fireworks R&D machines" had a security incident on Oct 23; on Oct 24 the attacker used it to reach Fireworks development machines and run "an unauthorized workload that led to additional customer data impact." This is Fireworks' second incident of the month; the first (Oct 6) involved secrets stored for evaluation jobs. Notion's advisory doesn't say which of the two its data came from; Wiz lists Notion's notice next to the second.
  • Nov 2–3 (Notion). Fireworks told Notion a small set of data had been accessed; Notion found it was "Notion AI synthetic testing data," then disconnected from Fireworks, deleted its data there and stopped all traffic to it.
  • Nov 6–8. Fireworks told Notion potential customer data may also have been accessed, and confirmed the final dataset on Nov 8. It "included Notion AI chat transcripts used for the Insights feature."
  • Nov 9. Notion contacted affected customers. Under 1% of workspaces are affected.

If you were contacted: find and rotate what you pasted

  1. Open the affected data the way Notion's email describes; Notion says affected customers can "retrieve and review the impacted data securely inside their workspace." The advisory doesn't give the incident window, so use the one in your email.

  2. Our note: search the transcripts for anything that looks like a credential, not just the keys you remember. Common prefixes: sk- and sk-proj- (OpenAI), sk-ant- (Anthropic), sk_live_ and rk_live_ (Stripe), AKIA (AWS), ghp_ and github_pat_ (GitHub), xoxb- (Slack), AIza (Google), plus connection strings with a password in them (postgres://user:pass@) and anything inside a pasted .env file.

  3. Rotate each one at the provider that issued it: create the replacement, update every place that uses it, then revoke the old value. Deleting the chat doesn't revoke anything. Change any password you pasted, and anywhere you reused it.

  4. Confirm the old values are dead. 401 means revoked:

    curl -s -o /dev/null -w "%{http_code}\n" \
      https://api.openai.com/v1/models \
      -H "Authorization: Bearer $OLD_OPENAI_API_KEY"
    
    curl -s -o /dev/null -w "%{http_code}\n" \
      https://api.stripe.com/v1/balance -u "$OLD_STRIPE_KEY:"

The general lesson: an AI chat is a third party you didn't vet

Our note: Notion's customers never chose Fireworks, and Fireworks' R&D machines sat on a cloud provider its customers never chose either. A key pasted into any AI assistant can end up with whoever runs inference, classification or logging behind it. NEAR AI, also on Wiz's list this week, found two customers' API keys "exposed in logs." Paste a placeholder (sk-...REDACTED) instead of the real value; the model doesn't need the secret to debug the code around it.

Want us to run it for you? The Ship Check Audit lists every key that ever left your server and confirms each old value now gets a 401 or 403: $149, within 48 hours.

Part of Black October

Wiz's "Black October" post now lists sixteen AI developer platforms with incidents since early October (as of its Nov 10 edit), and notes Notion's downstream notice under the Fireworks update. Every row, with what each vendor says to rotate: Black October: every AI dev platform breach in one list.

Ship Check Kit · $29

Rather not run it by hand?

The Ship Check Kit can't read your Notion chats. What it does: your coding agent finds every key that ever left your server (SC-SEC-01 for git history, SC-SEC-02 for the browser bundle) and SC-SEC-03 fails while any old value still gets anything but a 401 or 403. Three of 44 launch checks, each with the evidence and the fix.

Checked against Notion: Fireworks AI incident (updated Nov 10), Fireworks AI: Update on October 2026 security incident (Nov 9), NEAR AI: Security incident report (Nov 9), Wiz: "Black October" for AI Developer Platforms, Stripe: API keys on 2026-11-11. Only test apps and accounts you own or are allowed to test.