Case deepseek-db-exposureModel & data leakChina
DeepSeek leaves ClickHouse database with chat logs and API secrets open
Wiz found a publicly reachable DeepSeek ClickHouse database exposing over a million log lines including user chat history, API secrets and backend details; it was locked down after disclosure.
HighAttack on AIStatus: ResolvedVerified case file
Open in the interactive mapCite this case
- Reported
- Jan 29, 2025
- Location
- China
- Target
- DeepSeek
- Severity
- High
- Triggered by
- Misconfiguration by DeepSeek; found by Wiz Research (responsible disclosure)
- Actor type
- Accidental / misconfiguration
- Reported loss
- None reported
- CVE
- None
What happened
Wiz found a publicly reachable DeepSeek ClickHouse database exposing over a million log lines including user chat history, API secrets and backend details; it was locked down after disclosure.
Impact: Over one million log lines exposed: user chat history, API secret keys, backend details and operational metadata; Wiz said an attacker could have taken full control of the database and potentially escalated privileges
Who triggered it
Actor: Misconfiguration by DeepSeek; found by Wiz Research (responsible disclosure)
Attribution: Self-evident misconfiguration; discovered and disclosed by Wiz Research, which notified DeepSeek before publishing
Motive: None (accidental exposure); Wiz motive was security research
How it happened
Attack vector: Unauthenticated ClickHouse database reachable on ports 8123 and 9000 at oauth2callback.deepseek.com and dev.deepseek.com, queried via the HTTP interface
Root cause: Internal ClickHouse log database deployed with no authentication and exposed to the public internet; sensitive data (chat history, API keys) written to plaintext logs
Timeline
- Oldest entries in the exposed log_stream table are dated from this day
- Wiz Research finds the open database within minutes while assessing DeepSeek's external attack surface
- Wiz publishes findings after DeepSeek promptly locks down the database following disclosure
- Wide press coverage (BleepingComputer, Fortune) amid scrutiny of DeepSeek's security and privacy posture
Response
DeepSeek secured the database promptly after Wiz's disclosure; no public statement from DeepSeek on whether anyone else accessed the data
Current status: Resolved
Sources (open in a new tab)
- Wiz Research wiz.io
- BleepingComputer bleepingcomputer.com
- Fortune fortune.com
Cite this case
DeepSeek leaves ClickHouse database with chat logs and API secrets open. AI Threat Watch, case deepseek-db-exposure, Jan 29, 2025. https://aithreat.io/cases/deepseek-db-exposure/
Permanent link: https://aithreat.io/cases/deepseek-db-exposure/