AIToday
AI Safety & AlignmentAI Business & IndustryAI WeeklyPublished: Nov 7, 2026, 13:00 JST

Botpress breach exposes AI keys from 18 customer workspaces

Send on LINE
Botpress breach exposes AI keys from 18 customer workspaces

3 Key Points

  1. What happened

    Botpress disclosed on November 6, 2026 that an intruder used a flawed internal authentication proxy and an employee API credential to read bot configurations in 16 customer workspaces, with integration settings changed in two additional workspaces.

  2. Why it matters

    Botpress's logs cannot establish exactly which bots held a valid credential when read, so it is asking those customers to treat every credential stored in affected bots as exposed.

WHO IT HITSSecurity and platform teams at the 18 directly contacted Botpress customers must now rotate every credential stored in the affected bots and integrations, since the company cannot determine which were valid at the time of access.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

The incident began on October 12, 2026, when someone started probing the authentication proxy that protects several of Botpress's internal tools. A flaw in sign-in validation let the attacker in with sessions that appeared to belong to staff through October 21, 2026, giving visibility into customer account information and internal data, including staff API credentials. On October 21 between 07:44 and 08:23 UTC, the employee credential's administrator access was used to read configurations in 16 customer workspaces.

Botpress attributes the intrusion to an effort to obtain AI usage for resale on AI black markets, noting the attacker operated a large network of Botpress accounts to consume AI credits before and during the incident. The company says it has found no evidence that source code, build pipelines or published packages were changed, and no ransom demand has been received.

Containment came at approximately 16:25 UTC on October 21, when Botpress fixed the proxy vulnerability, rotated its secret and revoked the employee credential. The attacker kept attempting access through other routes afterward; Botpress says attempts observed through November 3, 2026 were rejected. Remaining work includes internal credential rotation and a review of when employees should hold administrator access to customer workspaces.

FAQ
How did the attacker get in?
The attacker probed an internal authentication proxy starting October 12, 2026 and used a flaw in its sign-in validation to enter with sessions that appeared to belong to Botpress staff.
What data was accessed?
Bot configurations in 16 workspaces, which can contain AI provider API keys and other third-party secrets; integration settings were also changed in two other workspaces.
Was customer conversation data exposed?
Botpress found no evidence of access to end-user conversations handled by customer bots.
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleOpenAI valued at $1.25 trillion with new $11 billion raise