Severity major: 17.6 million files totalling 22.72TB, including more than 144,000 AI chat logs with personal information, were left publicly accessible in a live production platform.
Earliest source we hold 2026-10-23
302.ai, an intermediary platform run by Univerads Technology Limited, gave customers access to major LLMs and stored chat logs and uploaded files in a Microsoft Azure bucket.
Risk grouping: Not yet classified
Before or after release
After release “The exposure occurred in 302.ai's storage infrastructure and does not establish that the AI model providers themselves suffered a breach.”source
The AI's part
Attacked “A security lapse at AI platform 302.ai left 17.6 million files totalling 22.72 terabytes publicly accessible, including more than 144,000 AI chat logs containing personal information and conversations linked to a prominent sex doll manufacturer, according to an investigation by Cybernews.”source
No source we hold states: who caused it, intended or not.
The story
1 · What it was doing302.ai, an intermediary platform run by Univerads Technology Limited, let customers use major LLMs including ChatGPT, Claude, Grok, DeepSeek and Gemini, and stored their chat logs and uploaded files in a Microsoft Azure bucket.
2 · What went wrongIts Azure storage bucket was left publicly accessible, exposing 17.6 million files and 22.72TB, including chat logs with personal data; Cybernews could not establish the specific security failure.
3 · What it reached or didThe archive held more than 144,000 chat logs with dates of birth, contact details and home addresses, plus images, videos, audio, documents and 26,000 ZIP files, including support chats of an unnamed sex doll manufacturer.
4 · How it was caughtCybernews researchers discovered the exposed data on 2 August 2026; no evidence was found that malicious actors had accessed or downloaded the files.
5 · What was doneAfter Cybernews contacted 302.ai, the storage was taken offline and observed closed on 8 September 2026; it is unresolved whether users were notified or further security changes made.
D inferred by us from the described behaviour, reason shown
Whose system
company using AI
D inferred by us from the described behaviour, reason shown
How it was connected
third-party AI intermediary platform
C one secondary source states it
What it was for
intermediary giving customers access to major large language models
C one secondary source states it
What happened
Earliest source we hold
2026-10-23
A the date the source itself carries
Who caught it
an independent researcher or journalist
C one secondary source states it
Near miss
yes, no harm happened
C one secondary source states it
Who was responsible
the organisation using it
D inferred by us from the described behaviour, reason shown
What was done
The exposed storage was closed.
C one secondary source states it
What went wrong
leaked private data
D inferred by us from the described behaviour, reason shown
AI agent
no AI agent acted
D inferred by us from the described behaviour, reason shown
Impact
Records exposed
17,600,000
C one secondary source states it
Severity
major
D inferred by us from the described behaviour, reason shown
Kind of harm
privacy
D inferred by us from the described behaviour, reason shown
Who was affected
17.6 million files totalling 22.72TB, including more than 144,000 AI chat logs and customer-support chats of a sex doll manufacturer
C one secondary source states it
Kinds of data exposed
personal information, chat logs, images, videos, audio, documents
C one secondary source states it
Why this severity
17.6 million files totalling 22.72TB, including more than 144,000 AI chat logs with personal information, were left publicly accessible in a live production platform.
D inferred by us from the described behaviour, reason shown
Context
Industry
AI platform / intermediary services
C one secondary source states it
Country
Hong Kong SAR China
C one secondary source states it
LR-2026-0240 · version 2 · published 2026-10-25 after automatic checks; not yet checked field by field by a person · changes to this case · JSON