Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download
DeepSeek AI

DeepSeek AI Vendor Cyber Rating & Cyber Score

deepseek.com

DeepSeek (深度求索), founded in 2023, is a Chinese company dedicated to making AGI a reality. Unravel the mystery of AGI with curiosity. Answer the essential question with long-termism. 🐋


DeepSeek AI A.I CyberSecurity Scoring

DeepSeek AI
Company Information
Website:https://www.deepseek.com
Employees number:154
Number of followers:184,520
NAICS:513
Industry Type:Technology, Information and Internet
Homepage:deepseek.com
DeepSeek AI Risk Score (AI oriented)
Between 0 and 549
logo
DeepSeek AITechnology, Information and Internet
Updated:
16/06/2026
486/1000
Critical
C
AaaAaABaaBaBCaaCaC
Powered by our proprietary A.I cyber incident model
Insurance prefers TPRM score to calculate premium
DeepSeek AI Global Score (TPRM)
xxxx
logo
DeepSeek AITechnology, Information and Internet
•••
Score locked
Instant access to detailed risk factors
Vulnerabilities
Benchmark vs. industry & size peers
Findings

DeepSeek AI
DeepSeek AICritical
Current Score
486C (CRITICAL)
01000
7 incidents
-54.5 avg impact
Incident timeline with MITRE ATT&CK tactics, techniques, and mitigations.
JUNE 2026
511Before Incident
Cyber Attack
16 Jun 2026DeepSeek AI
JetBrains, DeepSeek and OpenAI: Malicious JetBrains Marketplace plugins steal AI API keys from developers

Malicious JetBrains Plugins Steal AI API Keys in Large-Scale Campaign

486After Incident
CRITICAL-25
JETOPEDEE1781648632
Malicious JetBrains Plugins Steal AI API Keys in Large-Scale Campaign Security researchers at Aikido Security uncovered a coordinated malware campaign targeting developers via the JetBrains Marketplace, where at least 15 malicious plugins were designed to steal AI API keys from users. The plugins, disguised as legitimate AI coding assistants, code-review tools, and Git utilities, exploited integrations with services like OpenAI, DeepSeek, and SiliconFlow to harvest credentials. First published in October 2025, the plugins continued to appear as recently as June 10, 2026, with nearly 70,000 cumulative downloads. While functioning as advertised, they secretly transmitted API keys to a hardcoded server (39.107.60[.]51) via HTTP when users saved their credentials. All 15 plugins shared near-identical malicious code, despite being listed under seven different vendor accounts. Notably, the plugins offered a paid tier after users paid a small fee, the server provided an API key for model calls, replacing the user’s own credentials. Aikido Security noted this behavior was unusual, as legitimate operators would not distribute unrestricted paid API keys. The most downloaded plugins DeepSeek AI Assist (27,727 downloads) and CodeGPT AI Assistant (25,571 downloads) remained available on the Marketplace at the time of reporting. However, researchers cautioned that download counts could be inflated. BleepingComputer independently verified the credential-theft code in the DeepSeek AI Assist plugin. While malicious packages are common on platforms like npm and PyPI, such campaigns are rare on the JetBrains Marketplace. JetBrains had not responded to inquiries at the time of publication. The full list of compromised plugins includes tools like DeepSeek Git Commit, AI Coder Review, and Coding Simple Tool.
INCIDENT DETAILS -
TYPE
Malware Campaign
MOTIVATION
Credential theft, potential financial gain from stolen API keys
IMPACT
Data Compromised: AI API keys (OpenAI, DeepSeek, SiliconFlow)Systems Affected: Developer environments using JetBrains pluginsOperational Impact: Potential unauthorized access to AI services using stolen credentialsBrand Reputation Impact: Potential reputational damage to JetBrains Marketplace and affected AI service providers
DATA BREACH
Type Of Data Compromised: AI API keysNumber Of Records Exposed: Nearly 70,000 potential exposures (plugin downloads)Sensitivity Of Data: High (API keys for AI services)Data Exfiltration: Yes (transmitted to hardcoded server 39.107.60[.]51)
MAY 2026
504Before Incident
APRIL 2026
503Before Incident
MARCH 2026
495Before Incident
FEBRUARY 2026
490Before Incident
JANUARY 2026
487Before Incident
DECEMBER 2025
478Before Incident
NOVEMBER 2025
557Before Incident
Breach
11 Nov 2025DeepSeek AI
DeepSeek

Risks and Impacts of Shadow AI in Corporate Environments

473After Incident
CRITICAL-84
DEE3893138111125
DeepSeek, a Chinese AI provider, suffered a data breach linked to unsanctioned AI use, where sensitive corporate or user data—potentially including PII, proprietary code, or internal documents—was exposed due to employees inputting confidential information into unapproved AI models (e.g., public chatbots). The breach stemmed from shadow AI practices, where third-party AI tools (like DeepSeek’s own or others) stored and processed data without adequate security controls, leading to unauthorized access or leaks. The incident aligns with risks highlighted in the article: employees bypassing IT policies to use AI tools, resulting in data being retained on external servers with weaker protections. The breach not only violated data protection regulations (e.g., GDPR-like standards) but also risked further exploitation, such as adversaries accessing the leaked data or the AI model itself being compromised to exfiltrate additional information. The financial and reputational fallout included regulatory fines, loss of trust, and potential operational disruptions, compounded by the challenge of tracing all exposed data.
INCIDENT DETAILS -
TYPE
Data LeakageUnauthorized AI Usage (Shadow AI)Compliance ViolationOperational RiskThird-Party Risk
MOTIVATION
Employee productivity gains (unintentional risk)Corporate inertia in adopting sanctioned AI toolsFinancial gain (by threat actors exploiting shadow AI)
IMPACT
Financial Loss: Up to $670,000 per breach (IBM estimate); potential compliance fines (e.g., GDPR, CCPA)Personally Identifiable Information (PII)Intellectual Property (IP)Proprietary CodeMeeting NotesCustomer/Employee DataEmployee Devices (BYOD, laptops)Corporate Networks (via unauthorized AI agents)Business Software (AI features enabled without IT knowledge)Third-Party AI Servers (data storage in unregulated jurisdictions)Flawed decision-making due to biased/low-quality AI outputsIntroduction of exploitable bugs in customer-facing productsPotential corporate inertia or stalled digital transformationBrand Reputation Impact: High (due to data breaches, compliance violations, or flawed AI-driven decisions)Regulatory fines (e.g., GDPR, CCPA)Litigation from affected customers/employeesIdentity Theft Risk: High (if PII is shared with AI models or leaked)
DATA BREACH
PII (Customer/Employee)Intellectual PropertyProprietary CodeCorporate Meeting NotesSensitivity Of Data: High (regulated data under GDPR, CCPA, etc.)Data Exfiltration: Potential (via AI model training or third-party breaches)Personally Identifiable Information: Yes (shared with AI models or leaked)
OCTOBER 2025
556Before Incident
SEPTEMBER 2025
552Before Incident
AUGUST 2025
547Before Incident
JULY 2025
543Before Incident
JUNE 2025
657Before Incident
Breach
16 Jun 2025DeepSeek AI
DeepSeek

Shadow AI Data Leakage and Privacy Risks in Corporate Environments (2024-2025)

536After Incident
CRITICAL-121
DEE5293552111725
In early 2025, researchers at Wiz uncovered a vulnerable database operated by DeepSeek, exposing highly sensitive corporate and user data. The breach included chat histories, secret API keys, backend system details, and proprietary workflows shared by employees via the platform. The leaked data originated from shadow AI usage—employees bypassing sanctioned tools to use DeepSeek’s consumer-grade LLM for tasks involving confidential spreadsheets, internal memos, and potentially trade secrets. While no direct financial fraud or ransomware was confirmed, the exposure of authentication credentials and backend infrastructure details created a severe risk of follow-on attacks, such as spear-phishing, insider impersonation, or supply-chain compromises. The incident highlighted the dangers of ungoverned AI adoption, where ephemeral interactions with LLMs accumulate into high-value intelligence for threat actors. DeepSeek’s database misconfiguration enabled attackers to harvest years of prompt-engineered data, including employee thought processes, financial forecasts, and operational strategies—effectively handing adversaries a ‘master key’ to internal systems. Though DeepSeek patched the vulnerability, the breach underscored how shadow AI expands attack surfaces silently, with potential long-term repercussions for intellectual property theft, regulatory noncompliance (e.g., GDPR violations), and reputational damage. The exposure aligned with broader trends where 20% of organizations in an IBM study linked data breaches directly to unapproved AI tool usage, with average costs exceeding $670,000 per incident.
INCIDENT DETAILS -
TYPE
Data LeakagePrivacy ViolationShadow IT RiskAI Supply Chain VulnerabilityInsider Threat (Unintentional)
MOTIVATION
Financial Gain (e.g., $243,000 scam via AI voice cloning in 2019)Corporate EspionageData Harvesting for Dark Web SalesDisruption of Business OperationsExploitation of AI Training Data
IMPACT
Financial Loss: Up to $670,000 per breach (IBM 2025); Potential GDPR fines up to €20M or 4% global revenueProprietary Code (e.g., Samsung 2023 incident)Financial Records (22% of UK employees use shadow AI for financial tasks)Internal Memos/Trade SecretsEmployee Health RecordsClient Data (58% of employees admit sharing sensitive data)Chat Histories (e.g., DeepSeek’s exposed database)Secret Keys/Backend DetailsCorporate AI Tools (e.g., Slack AI)Third-Party LLMs (ChatGPT, Claude, DeepSeek)Enterprise Workflows Integrating Unsanctioned AILegal/Compliance Systems (Data retention conflicts)Loss of Intellectual PropertyErosion of Competitive AdvantageDisruption of Internal Communications (e.g., AI-drafted memos leaking secrets)Increased Scrutiny from RegulatorsRevenue Loss: Potential 4% global revenue (GDPR fines) + breach costsCustomer Complaints: Likely (due to privacy violations)Brand Reputation Impact: High (publicized breaches, regulatory actions)GDPR Noncompliance (Fines up to €20M)Lawsuits (e.g., New York Times vs. OpenAI 2025)Contractual Violations with ClientsIdentity Theft Risk: High (AI-generated impersonation attacks)Payment Information Risk: Moderate (22% use shadow AI for financial tasks)
DATA BREACH
Chat HistoriesProprietary CodeFinancial DataInternal DocumentsSecret KeysBackend System DetailsEmployee/Patient Health RecordsTrade SecretsNumber Of Records Exposed: Unknown (potentially millions across affected platforms)Sensitivity Of Data: High (includes PII, financial, proprietary, and health data)Data Exfiltration: Confirmed (e.g., DeepSeek, Slack AI, Shadow AI leaks)Data Encryption: Partial (e.g., OpenAI encrypts data at rest, but retention policies create risks)Text (prompts/outputs)Spreadsheets (e.g., confidential financial data)Code RepositoriesAudio (e.g., voice cloning samples)Internal MemosPersonally Identifiable Information: Yes (employee/client records, health data)
MAY 2025
659Before Incident
Vulnerability
01 May 2025DeepSeek AI
Deepseek, Anthropic, OpenAI, n8n and Flowise: We Scanned 1 Million Exposed AI Services. Here's How Bad the Security Actually Is

AI Infrastructure Security Crisis: Exposed Systems, Hardcoded Flaws, and Rampant Misconfigurations

654After Incident
CRITICAL-5
FLODEEANTOPEN8N1777984637
AI Infrastructure Security Crisis: Exposed Systems, Hardcoded Flaws, and Rampant Misconfigurations A recent investigation by the Intruder team reveals a alarming trend in AI infrastructure security, as rapid adoption outpaces safeguards. Scanning over 2 million hosts with 1 million exposed services, researchers found AI deployments riddled with vulnerabilities more severe than any other software category they’ve analyzed. No Authentication by Default A core issue: many self-hosted AI projects ship without authentication enabled, leaving sensitive data and tools exposed. Real-world examples included chatbots with unrestricted access to user conversation histories, multimodal LLMs vulnerable to jailbreaking, and even NSFW chatbots leaking API keys in plaintext. One OpenUI-based instance exposed full LLM conversation logs, while others allowed malicious users to bypass safety guardrails using corporate infrastructure to generate illegal content or solicit criminal advice. Exposed Agent Platforms and Business Logic Agent management platforms like n8n and Flowise were frequently found misconfigured, with some instances mistakenly exposed to the internet. One Flowise deployment revealed an entire LLM chatbot’s business logic, including credential lists (though stored values remained protected). Another exposed parsing tools and local functions capable of server-side code execution. Across sectors government, finance, and marketing over 90 exposed instances were identified, enabling attackers to modify workflows, redirect traffic, or poison responses. Unsecured Ollama APIs: A Gateway to Frontier Models Researchers discovered 5,200+ exposed Ollama APIs with connected models, 31% of which responded to unauthenticated queries. While Ollama doesn’t store conversation data, many instances wrapped paid models from Anthropic, Google, Deepseek, Moonshot, and OpenAI 518 in total. Responses ranged from health-focused assistants to cloud management integrations, highlighting the risks of unauthorized access to enterprise systems. Insecure by Design Lab analysis uncovered systemic flaws: - Poor deployment practices: Misconfigured Docker setups, hardcoded credentials, and applications running as root. - No authentication on fresh installs: Users granted high-privilege access by default. - Static credentials: Embedded in setup examples and `docker-compose` files. - New vulnerabilities: Arbitrary code execution found in a popular AI project within days. Root Cause: Speed Over Security The findings underscore a broader industry shift vendors and adopters prioritizing rapid deployment over decades of security best practices. While some projects abandon safeguards entirely, the pressure to outpace competitors exacerbates the problem. The result: AI infrastructure with a 2.6 CVE-per-day average (as seen in the ClawdBot incident), where misconfigurations and weak sandboxing amplify risks. The investigation serves as a stark reminder of the security debt accumulating in the AI gold rush.
INCIDENT DETAILS -
TYPE
MisconfigurationAuthentication BypassData ExposureCode Execution
MOTIVATION
Opportunistic ExploitationData TheftUnauthorized Access
IMPACT
LLM conversation logsAPI keysBusiness logicCredential listsUser conversation historiesPersonally identifiable informationSelf-hosted AI projectsAgent management platforms (n8n, Flowise)Ollama APIsMultimodal LLMsChatbotsNSFW chatbotsUnauthorized modification of workflowsTraffic redirectionResponse poisoningServer-side code executionBrand Reputation Impact: HighIdentity Theft Risk: High
DATA BREACH
LLM conversation logsAPI keysBusiness logicCredential listsUser conversation historiesSensitivity Of Data: HighPersonally Identifiable Information: Yes
FEBRUARY 2025
659Before Incident
Vulnerability
01 Feb 2025DeepSeek AI
DeepSeek

DeepSeek Data Leak

652After Incident
CRITICAL-7
DEE001021525
DeepSeek, a generative AI platform, faced heightened concerns over privacy and security as it stores user data on servers in China. Security researchers discovered that DeepSeek exposed a critical database online, leaking over 1 million records, including user prompts, system logs, and API authentication tokens. The leaked information could lead to unauthorized access and misuse of user data, posing serious privacy and security risks. Furthermore, the platform's safety protections were found to be lacking when tested against various jailbreaks, illustrating a potential vulnerability to cyber threats.
INCIDENT DETAILS -
TYPE
Data Leak
IMPACT
user promptssystem logsAPI authentication tokens
DATA BREACH
user promptssystem logsAPI authentication tokensNumber Of Records Exposed: 1 million
JANUARY 2025
677Before Incident
Cyber Attack
27 Jan 2025DeepSeek AI
DeepSeek: DeepSeek hit with large-scale cyberattack, says it's limiting registrations

DeepSeek R1 AI Model Service Disruption Due to Large-Scale Malicious Attacks

659After Incident
HIGH-18
DEE1774745353
DeepSeek’s R1 AI Model Disrupts Industry Amid Cyberattack and Soaring Demand Chinese AI startup DeepSeek has rapidly emerged as a major player in the generative AI race, drawing global attention after the release of its R1 reasoning model a low-cost, open-source alternative to OpenAI’s o1. Founded in April 2023 from a hedge fund’s AI research unit, DeepSeek has positioned itself as a challenger to industry leaders like OpenAI and Google, with ambitions to achieve artificial general intelligence (AGI). The R1 model, launched last week, has been praised for its performance and cost efficiency, reportedly trained for just $5.6 million a fraction of the expense behind rival models. Its open-source availability has fueled adoption, propelling DeepSeek’s AI Assistant app to the top of Apple’s U.S. App Store, briefly dethroning ChatGPT as the most-downloaded free app. However, the surge in popularity has come with security challenges. On Monday, DeepSeek announced temporary registration limits due to "large-scale malicious attacks" on its services, though existing users remain unaffected. The incident underscores the growing cyber risks facing high-profile AI platforms as they gain traction. DeepSeek’s rapid rise has also sparked debate about the sustainability of AI funding, with analysts questioning whether the industry’s billion-dollar valuations and aggressive spending are justified. Despite its lower development costs, the startup’s success signals a shift in the AI landscape, particularly as Chinese firms advance despite U.S. restrictions on high-end chip access. The company’s trajectory highlights the intensifying competition in AI, where cost efficiency and open-source innovation are reshaping the market.
INCIDENT DETAILS -
TYPE
Cyberattack
IMPACT
Systems Affected: DeepSeek AI services (registration system)Operational Impact: Temporary registration limits imposed
JANUARY 2025
770Before Incident
Breach
01 Jan 2025DeepSeek AI
DeepSeek

DeepSeek Data Leak via Publicly Accessible ClickHouse Database

675After Incident
CRITICAL-95
DEE456090325
In January 2025, Chinese AI specialist DeepSeek suffered a critical data leak exposing over 1 million sensitive log streams, including chat histories, secret keys, and internal operational data. The breach stemmed from a publicly accessible ClickHouse database with misconfigured access controls, granting unauthorized parties full administrative privileges—enabling potential data exfiltration, manipulation, or deletion. While Wiz Research promptly alerted DeepSeek, which secured the exposure, the incident highlighted vulnerabilities in cloud storage misconfigurations and endpoint security. The leaked data posed risks of intellectual property theft, credential compromise, and regulatory non-compliance (e.g., GDPR/CCPA fines). Given the scale and sensitivity of the exposed logs—likely containing proprietary AI model interactions and authentication tokens—the breach could undermine customer trust, competitive advantage, and operational integrity, with potential downstream effects like fraud, reputational damage, or supply chain attacks. The root cause aligned with unintentional leakage via misconfigured infrastructure, though insider threats or targeted exploitation remained plausible secondary risks.
INCIDENT DETAILS -
TYPE
Data Leak
IMPACT
Chat HistorySecret KeysLog Streams (1M+ records)ClickHouse DatabaseOperational Impact: High (Exposure of Sensitive Internal Data)Brand Reputation Impact: Potential Long-Term Damage (Unquantified)Potential GDPR Fines (EU)Potential CCPA Fines (California)Identity Theft Risk: High (Exposure of Secret Keys)Payment Information Risk: Potential (If Secret Keys Included Payment-Related Credentials)
DATA BREACH
Log StreamsChat HistorySecret KeysNumber Of Records Exposed: 1,000,000+Sensitivity Of Data: High (Includes Authentication Credentials and Internal Communications)Data Encryption: No (Data Was Publicly Accessible)Log FilesPotential Configuration Files

Frequently Asked Questions

?
What is the current A.I Rankiteo Cyber Score for DeepSeek AI ?
?
What was DeepSeek AI's A.I Rankiteo Cyber Score in May 2026 ?
?
What was DeepSeek AI's A.I Rankiteo Cyber Score in April 2026 ?
?
What was DeepSeek AI's A.I Rankiteo Cyber Score in March 2026 ?
?
What was DeepSeek AI's A.I Rankiteo Cyber Score in February 2026 ?
?
What was DeepSeek AI's A.I Rankiteo Cyber Score in January 2026 ?
?
What was DeepSeek AI's A.I Rankiteo Cyber Score in December 2025 ?
?
What was DeepSeek AI's A.I Rankiteo Cyber Score in November 2025 ?
?
What was DeepSeek AI's A.I Rankiteo Cyber Score in October 2025 ?
?
What was DeepSeek AI's A.I Rankiteo Cyber Score in September 2025 ?
?
What was DeepSeek AI's A.I Rankiteo Cyber Score in August 2025 ?
?
What was DeepSeek AI's A.I Rankiteo Cyber Score in July 2025 ?
?
What is the average per-incident point impact on DeepSeek AI's A.I Rankiteo Cyber Score over the past 12 months ?
?
Where can I access detailed records of all cyber incidents associated with DeepSeek AI ?
?
Where can I find a summary of the A.I Rankiteo Risk Scoring methodology ?
?
Where can I view DeepSeek AI's profile page on Rankiteo ?
?
How accurate is the A.I Rankiteo Risk Scoring methodology ?