/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Wiz: DeepSeek left one of its critical databases exposed, leaking more than 1M records including system logs, user prompt submissions, and users' API keys

China-based DeepSeek has exploded in popularity, drawing greater scrutiny.  Case in point: Security researchers found more than 1 million records …

Wired

Context & Ripple Effects

DeepSeek’s rapid rise had already brought attention to its policy of storing user-provided model content on servers in China. This exposure makes the security handling of that data an operational issue, not solely a disclosure-policy question.

It also arrives as Microsoft and OpenAI were reportedly examining suspected unauthorized API data acquisition tied to a DeepSeek-linked group, increasing scrutiny of the company’s data-access controls from multiple directions.

First-order effects

  • DeepSeek must secure the exposed database and assess the impact on people whose prompts, system logs, and API keys were included in the more than 1 million records.
  • Affected API users may need to rotate credentials and review usage, while exposed prompts and logs create a potential confidentiality concern for users of the service.

Second-order effects

  • Enterprise users and prospective customers are likely to subject DeepSeek’s data handling and deployment controls to closer review, especially given the company’s stated collection and storage practices.
  • Competing AI providers can position security controls, credential management, and clearer data-governance practices as differentiators when customers evaluate model platforms.

Third-order effects

  • If prominent AI labs repeatedly pair rapid adoption with exposed operational data, security maturity will become more central to the legitimacy of their data practices and to enterprise procurement decisions.
  • The episode points toward AI services being judged not only on model capability and price, but on the resilience of the infrastructure that stores prompts, logs, and access credentials.

The trend: As AI platforms scale quickly, infrastructure security and data governance are becoming core competitive requirements alongside model performance.

Discussion

  • @lukaszolejnik Lukasz Olejnik on bluesky
    Cybersecurity of AI systems.  DeepSeek database (leak?) was accessible publicly (development servers oauth2callback.deepseek.com:9000 and dev.deepseek.com:9000), contained some chat histories.  Since it was public, it could've leaked or be stolen, with highly sensitive data. www.…
  • @mattburgess1 Matt Burgess on bluesky
    NEW: DeepSeek left a database exposed to the web.  —  It contained more than one million files, including prompts and API keys, researchers at cloud security firm Wiz say  —  Story with @lhn.bsky.social
  • @braithwaite.dev Alan on bluesky
    Interesting and serious vuln in DeepSeek's dev infra found by Wiz https://buff.ly/4jBy42s  —  Obviously an observability database, but ofc chat logs got in there.  —  Rocket building prompts in the post.  But most likely it's training data to prevent the AI from responding.
  • @marypcbuk Mary Branscombe on bluesky
    that DeepSeek outage? yeah, they really weren't ready for people to take much of an interest because they hadn't remembered to secure their ClickHouse database so um yikes
  • @nathanpeck.com Nathan Peck on bluesky
    Phew this is a spicy one: DeepSeek apparently had a misconfigured DB that allowed anyone to connect to the DB and query chat conversations.  Huge privacy breach!  —  And that's why you run models local, or use a trustworthy API like Bedrock, instead of using startup APIs: www.wiz…
  • @marko.social Marko Bevc on bluesky
    Well, that didn't take very long 😜  —  www.wiz.io/blog/wiz-res...  #AI #security
  • @LukaszOlejnik@mastodon.social Lukasz Olejnik on mastodon
    DeepSeek database was accessible publicly (development servers oauth2callback.deepseek.com:9000 and dev.deepseek.com:9000), contained some chat histories.  Since it was public, it could have leaked or be stolen, with highly sensitive data. https://www.wiz.io/...  [image]
  • @mavolpi Mike Volpi on x
    .@deepseek_ai using @ClickHouseDB. I guess they know how to use the best.... https://www.wiz.io/...
  • @lostinsecurity David Barroso on x
    We all agree that @deepseek_ai should level up their security, but since when do companies try to compromise other companies without any bug bounty or authorization?
  • @wiz_io @wiz_io on x
    BREAKING: Internal #DeepSeek database publicly exposed 🚨 Wiz Research has discovered “DeepLeak” - a publicly accessible ClickHouse database belonging to DeepSeek, exposing highly sensitive information, including secret keys, plain-text chat messages, backend details, and logs. [i…
  • @ceo_clickhouse Aaron Katz on x
    Great to see @deepseek_ai using @ClickHouseDB to handle logging at scale. ClickHouse does not allow external connections by default. If someone wants to configure an unauthenticated access from the Internet, they have to do the following extra steps: - enable listening to the
  • @miguel_de_vega Miguel de Vega on x
    Collecting sensitive information you don't need to run your service and failing to protect it is a double felony in privacy land You can't leak what you can't see. That's why @nillionnetwork enables developers to build and deploy applications on infrastructure where nodes never
  • @mayazi Maya Zehavi on x
    It's almost like DeepSeek is a honeypot open to all for the grab. A good lesson as to what kind of security & privacy concerns users need to be warned of.
  • @wiz_io @wiz_io on x
    📌 Takeaways for security teams → AI security starts with infrastructure: lock down databases & access controls. → Visibility is key: work closely with AI engineers to map out risks. Read the full research 👇 https://www.wiz.io/...
  • @dcuthbert Daniel Cuthbert on x
    “(Note: We did not execute intrusive queries beyond enumeration to preserve ethical research practices.)” https://www.wiz.io/... Whilst the research is solid, I do question what ethical paths were taken here given if this was the other way around, we'd be crying.
  • @0ceans404 @0ceans404 on x
    “no one cares about privacy” “privacy isn't sexy” “privacy enhancing tech isn't worth the trouble” until 👇🧵
  • @joab_jackson Joab Jackson on x
    “And for the record if you are using open tools to point to something like DeepSeek, you are straight up going to get hurt.” — @cmcluck @StackLokHQ https://www.wiz.io/...
  • r/programmingHungary r on reddit
    Wiz Research Uncovers Exposed DeepSeek Database Leaking Sensitive Information, Including Chat History
  • r/cybersecurity r on reddit
    Wiz Research Uncovers Exposed DeepSeek Database Leaking Sensitive Information, Including Chat History |  Wiz Blog
  • r/technews r on reddit
    Exposed DeepSeek Database Revealed Chat Prompts and Internal Data
  • r/LocalLLaMA r on reddit
    Wiz Research Uncovers Exposed DeepSeek Database Leaking Sensitive Information, Including Chat History