> JapanHacked_
[Investigating][Severity: Moderate][Intrusion]

ONE CAREER, TRUSTDOCK, Yayoi and others: intrusion at Notion AI supplier Fireworks AI exposes AI chat records

An intrusion at Fireworks AI, which processed Notion AI data, may have exposed Japanese companies' staff chats with the AI, holding names and contacts of clients and users.

Disclosed

2026-11-11

Organizations involved

13

Leaked or at risk

2.3K

2,300

Downtime

Unknown

What happened

According to Notion Labs, Fireworks AI, a US company that Notion used to classify Notion AI usage for its Insights feature among other tasks, reported unauthorized access to some data on the night of 2 November. Notion cut its connection to Fireworks and deleted the data there by the morning of 3 November. On 6 November Fireworks said customer data may also have been accessed, and a new dataset confirmed on 8 November contained Notion AI chats used for Insights. Notion announced this on 9 November, US time. Fewer than 1% of workspaces are affected, and most records carry no user or workspace identifiers. [1] [16]

The records were mostly created from about 5 to 24 October 2026 and contain what employees typed into Notion AI and the AI's replies. Yayoi says Notion told it that Fireworks had kept input and output data against the terms of their agreement. Notion pages, databases and attachments are not affected. Notion revoked the Notion API keys found in the records and reported other providers' keys to their issuers. The Insights feature and models served through Fireworks are suspended. [1] [11] [15]

Affected companies in Japan

From 11 to 13 November, Japanese companies notified by Notion disclosed the incident one after another. None of their own systems or services was accessed. All say it is not yet known whether a third party obtained the records, treat them as leaked and are contacting the people concerned. No misuse has been found. [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14]

What users should do

In notified workspaces, change any password or API key pasted into Notion AI during this period. Beware of suspicious email or calls posing as the companies or Notion. [1] [7]

Timeline

  1. Detected 2026-11-06
  2. Disclosed 2026-11-11
  3. 5 days

Attack or cause

Method
[Intrusion]
Impact
[Data leak]
Entry point
Supplier

Data exposed or at risk

[Name][E-mail address][Phone number]

Supply chain

Organizations involved

Open in organization search

Sources

  1. [1][Official]Fireworks AIのインシデントについてNotion · 2026-11-13
  2. [2][Official]当社が利用するクラウドサービスの委託先への不正アクセスに伴う、AI機能での入力情報の流出の可能性に関するお知らせ(第一報)LRM · 2026-11-11
  3. [3][Official]当社が利用するクラウドサービスの委託先への不正アクセスに伴う、お客様に関する情報漏えいの可能性についてのお詫びとお知らせ(第一報)SecureNavi · 2026-11-11
  4. [4][Official]外部委託先への不正アクセスによる、社内情報の一部の情報漏えいの可能性についてTRUSTDOCK · 2026-11-11
  5. [5][Official]当社が利用するクラウドサービスの委託先への 不正アクセスに伴う、AI機能での入力情報の 流出のおそれに関するお知らせとお詫び(第一報)THIRD · 2026-11-11
  6. [6][Official]Notion AIに入力した情報の流出の可能性に関するお知らせ(第一報)Faeger · 2026-11-11
  7. [7][Official]外部サービス「Notion」のAI機能における情報流出の可能性に関するお知らせとお詫び(第一報)ONE CAREER · 2026-11-12
  8. [8][Official]当社が利用するクラウドサービスの委託先への不正アクセスによる情報流出の可能性に関するお知らせRECEPTIONIST
  9. [9][Official]【お詫びとお知らせ】当社が業務で利用する外部サービスにおける不正アクセスに伴う情報漏えいの可能性についてTimeTree · 2026-11-12
  10. [10][Official]当社利用クラウドサービスの委託先における不正アクセスによる個人情報漏えいのおそれに関するお知らせとお詫びInteractive · 2026-11-12