The security firm found two publicly accessible database instances at oauth2callback.deepseek.com:9000 and dev.deepseek.com:9000 that allowed arbitrary SQL queries via a web interface without requiring authentication.

The databases contained a 'log_stream' table that stored sensitive internal logs dating from January 6, 2025, containing:

  • user queries to DeepSeek's chatbot,
  • keys used by backend systems to authenticate API calls,
  • internal infrastructure and services information, 
  • and various operational metadata.
Chat log in plaintext
Chat log in plaintext
Source: Wiz

"This level of access posed a critical risk to DeepSeek's own security and for its end-users," comments Wiz.

  • "Not only an attacker could retrieve sensitive logs and actual plaintext chat messages, but they could also potentially exfiltrate plaintext passwords and local files along propriety information directly from the server using queries like: SELECT * FROM file('filename') depending on their ClickHouse configuration."
Exposed data
Exposed data