mythsthe AIDeepSeek exposed database2025ai

everyone assumed:

the AI vendor secures the prompts we send it

what was actually true:

The security of your prompts is exactly as good as the vendor's weakest configuration, which you cannot see and did not vet.

how it happened

  1. whoanyone onlineno credentials needed
  2. the gapexposed log storequeryable from a browser
  3. the result1M+ log lineschat history and secret keys
the gap that let it happen the result

what everyone assumed

Sending a prompt to an established-looking AI tool feels like handing it to a competent operator who will protect it. The assumption is that the vendor has secured the back end, because securing the back end is the vendor’s basic job.

what happened

The exposed database accepted queries from anyone, returning plaintext chat history, API keys, and backend secrets through a browser. The prompts users assumed were protected were sitting in an open store, alongside the keys to the service itself.

step by step

  1. a database is left open to the internetIt accepts queries from anyone, no credentials needed.the assumption breaks here
  2. chat history and secrets sit insidePlaintext prompts, API keys and backend secrets.
  3. January 2025Wiz Research finds and discloses itOver a million log lines reachable through a browser.

how it surfaced

In January 2025 Wiz Research disclosed the open DeepSeek database: over a million log lines including plaintext chat history and secret keys, reachable with no credentials.

The security of your prompts is exactly as good as the vendor’s weakest configuration, which you cannot see and did not vet.

Trusting a tool with data is trusting an operation you have not inspected.

picture it at a company like yours

The company here is made up. The other two paths are not: they happened, and each links to the story.

your company
a normal dayYour staff paste client notes into a new AI tool because it is quick and free.
the gap nobody seesNobody checked how the vendor stores that data.company data flowing into AI tools nobody vetted
  1. in this story
    the day it mattersResearchers find the vendor's database open to the internet, chats included.
    what it costs youYour client notes were readable by anyone who looked, and you never chose that vendor.
  2. or it goes like this
    howEngineers paste code and notes into a free chatbot to get help.
    what leavesconfidential code and meeting noteswho ends up with itan AI vendor on consumer terms
    it happenedSamsung, 2023
  3. or it goes like this
    howA shared chat link becomes public with one checkbox.
    what leavesclient names and personal detailswho ends up with itanyone using a search engine
    it happenedChatGPT shared links, 2025

sources

  1. Wiz Blog, January 2025

← all myths

your turn

what you can do about it

  1. this week

    List the AI tools that hold your company's data, and whether anyone vetted the vendor.

    Your teams send company information into AI tools daily, on the assumption the vendor has locked the back end. DeepSeek is proof that assumption can be entirely wrong. Which AI tools hold your data, and whether anyone checked the vendor before the data started flowing, is the gap here.

  2. go deeper

  3. if you're not sure where to start

    Run the offboarding checklist on one leaver. It covers every account and token to close when someone leaves.

    open the checklist →

the letter · every two weeks

one access gap in your inbox, with the fix.

Every issue takes one way access creeps in, shows a real incident where it went wrong, and ends with one thing to check that week. Written for the people who run the tools, without a security team behind them.

  • 1one mechanism, explained plainly
  • 2one real incident, taken apart
  • 3one step you can take on Monday

get the next issue

One email every two weeks. Your address stays here and is never passed to vendors. One click to unsubscribe. Privacy.