Skip to content

Malicious JetBrains Marketplace Plugins Steal AI API Keys

At least 15 malicious plugins were discovered on the JetBrains Marketplace, designed to steal AI API keys from developers. The plugins, published under seven vendor accounts, have been installed close to 70,000 times.

Severity awaiting reviewSupply chain
Incident date
Published
Read time
9 min
C
CertGPS

Not independently reviewed

AI-assisted content. Editorial policy ยท Suggest a correction

View source
On this page

Note: This analysis is based on publicly available information from source article. Facts are clearly separated from technical analysis.

Executive Summary

In October 2025, malicious plugins were first published on the JetBrains Marketplace, a platform for developers to discover and install plugins for their coding tools. These plugins, disguised as AI coding assistants, code-review tools, and Git utilities, were actually designed to steal AI API keys from unsuspecting users. The plugins, powered by popular AI services such as OpenAI, DeepSeek, and SiliconFlow, exfiltrated API keys entered by users into plugin settings and sent them to a hardcoded server. The incident continued for at least 8 months, affecting 70,000 devices and 7 vendor accounts. This incident highlights the importance of supply-chain security and the need for developers to be cautious when installing plugins from untrusted sources.

The severity of this incident is high, as it compromised the security of multiple AI services and potentially allowed attackers to access sensitive data. The fact that the plugins were able to operate undetected for so long is a testament to the sophistication of the attackers and the need for improved security measures.

What Happened: Timeline

โœ… Verified Facts

  • October 2025: Malicious plugins first published on JetBrains Marketplace
  • June 10, 2026: New plugins published, continuing the malicious campaign
  • June 16, 2026: Article published, exposing the incident

Technical Deep Dive

Understanding AI Coding Assistants

What is it?

AI coding assistants are software tools that use machine learning algorithms to provide developers with suggestions and recommendations for their code. These tools can help developers write more efficient and effective code, but they can also be used to steal sensitive information.

How does it work?

AI coding assistants typically work by analyzing the code that a developer is writing and providing suggestions based on that analysis. They may also use machine learning algorithms to predict the behavior of the code and provide recommendations for improvement.

Security considerations

The security of AI coding assistants is a concern because they often require access to sensitive information, such as API keys. If an attacker is able to compromise an AI coding assistant, they may be able to steal sensitive information or use the assistant to launch further attacks.

OpenAI is a popular AI service that provides developers with access to a range of machine learning models and tools. OpenAI's API allows developers to integrate its models into their own applications, but it also requires developers to provide sensitive information, such as API keys.

DeepSeek is another popular AI service that provides developers with access to a range of machine learning models and tools. Like OpenAI, DeepSeek's API requires developers to provide sensitive information, such as API keys.

Analysis: What Went Wrong

๐Ÿ“Š Professional Analysis

Technical Root Cause

The technical root cause of this incident was the failure of JetBrains to properly vet the plugins that were published on its marketplace. The plugins were able to operate undetected for so long because they were able to masquerade as legitimate plugins and avoid detection by JetBrains' security measures.

Contributing Factors

The contributing factors to this incident were the lack of awareness among developers about the risks associated with installing plugins from untrusted sources and the failure of JetBrains to provide adequate security measures to protect its users.

Lessons for Security Professionals

Key Takeaways

  1. Be cautious when installing plugins from untrusted sources: Developers should be aware of the risks associated with installing plugins from untrusted sources and should take steps to verify the legitimacy of any plugin before installing it.
  2. Implement robust security measures: Developers and organizations should implement robust security measures to protect their users and their data.
  3. Monitor for suspicious activity: Developers and organizations should monitor for suspicious activity and take steps to detect and respond to potential security incidents.

Prevention & Detection

How to Prevent

  • Verify the legitimacy of plugins: Developers should verify the legitimacy of any plugin before installing it.
  • Use secure coding practices: Developers should use secure coding practices to prevent vulnerabilities in their code.
  • Implement robust security measures: Developers and organizations should implement robust security measures to protect their users and their data.

How to Detect

  • Monitor for suspicious activity: Developers and organizations should monitor for suspicious activity and take steps to detect and respond to potential security incidents.
  • Use security tools: Developers and organizations should use security tools to detect and respond to potential security incidents.
  • Implement incident response plans: Developers and organizations should implement incident response plans to respond to potential security incidents.
View related certification topics

Security+

  • Security and Risk Management: This domain relates to the security considerations of AI coding assistants and the need for developers to be cautious when installing plugins from untrusted sources.
  • Threats and Vulnerabilities: This domain relates to the technical root cause of this incident, which was the failure of JetBrains to properly vet the plugins that were published on its marketplace.

CEH

  • Malware Analysis: This domain relates to the technical analysis of the malicious plugins and the need for developers to be aware of the risks associated with installing plugins from untrusted sources.
  • Web Application Security: This domain relates to the security considerations of AI coding assistants and the need for developers to use secure coding practices to prevent vulnerabilities in their code.

CISSP

  • Security and Risk Management: This domain relates to the security considerations of AI coding assistants and the need for developers to be cautious when installing plugins from untrusted sources.
  • Threats and Vulnerabilities: This domain relates to the technical root cause of this incident, which was the failure of JetBrains to properly vet the plugins that were published on its marketplace.

OSCP

  • Penetration Testing: This domain relates to the technical analysis of the malicious plugins and the need for developers to be aware of the risks associated with installing plugins from untrusted sources.
  • Web Application Security: This domain relates to the security considerations of AI coding assistants and the need for developers to use secure coding practices to prevent vulnerabilities in their code.

CISM

  • Information Security Governance: This domain relates to the security considerations of AI coding assistants and the need for developers to be cautious when installing plugins from untrusted sources.
  • Risk Management: This domain relates to the technical root cause of this incident, which was the failure of JetBrains to properly vet the plugins that were published on its marketplace.

CISA

  • Information Systems Security: This domain relates to the security considerations of AI coding assistants and the need for developers to be cautious when installing plugins from untrusted sources.
  • Risk Management: This domain relates to the technical root cause of this incident, which was the failure of JetBrains to properly vet the plugins that were published on its marketplace.

GSEC

  • Security and Risk Management: This domain relates to the security considerations of AI coding assistants and the need for developers to be cautious when installing plugins from untrusted sources.
  • Threats and Vulnerabilities: This domain relates to the technical root cause of this incident, which was the failure of JetBrains to properly vet the plugins that were published on its marketplace.

SecurityX

  • Security and Risk Management: This domain relates to the security considerations of AI coding assistants and the need for developers to be cautious when installing plugins from untrusted sources.
  • Threats and Vulnerabilities: This domain relates to the technical root cause of this incident, which was the failure of JetBrains to properly vet the plugins that were published on its marketplace.

Network+

  • Network Security: This domain relates to the security considerations of AI coding assistants and the need for developers to be cautious when installing plugins from untrusted sources.
  • Threats and Vulnerabilities: This domain relates to the technical root cause of this incident, which was the failure of JetBrains to properly vet the plugins that were published on its marketplace.

CRISC

  • Risk Management: This domain relates to the technical root cause of this incident, which was the failure of JetBrains to properly vet the plugins that were published on its marketplace.
  • Information Systems Security: This domain relates to the security considerations of AI coding assistants and the need for developers to be cautious when installing plugins from untrusted sources.

AWS Security

  • Security and Compliance: This domain relates to the security considerations of AI coding assistants and the need for developers to be cautious when installing plugins from untrusted sources.
  • Threats and Vulnerabilities: This domain relates to the technical root cause of this incident, which was the failure of JetBrains to properly vet the plugins that were published on its marketplace.

AZ-500

  • Security and Compliance: This domain relates to the security considerations of AI coding assistants and the need for developers to be cautious when installing plugins from untrusted sources.
  • Threats and Vulnerabilities: This domain relates to the technical root cause of this incident, which was the failure of JetBrains to properly vet the plugins that were published on its marketplace.

GPEN

  • Security and Risk Management: This domain relates to the security considerations of AI coding assistants and the need for developers to be cautious when installing plugins from untrusted sources.
  • Threats and Vulnerabilities: This domain relates to the technical root cause of this incident, which was the failure of JetBrains to properly vet the plugins that were published on its marketplace.

GCIH

  • Security and Risk Management: This domain relates to the security considerations of AI coding assistants and the need for developers to be cautious when installing plugins from untrusted sources.
  • Threats and Vulnerabilities: This domain relates to the technical root cause of this incident, which was the failure of JetBrains to properly vet the plugins that were published on its marketplace.

CSSLP

  • Security and Risk Management: This domain relates to the security considerations of AI coding assistants and the need for developers to be cautious when installing plugins from untrusted sources.
  • Threats and Vulnerabilities: This domain relates to the technical root cause of this incident, which was the failure of JetBrains

Source (1)

This analysis is based on: https://www.bleepingcomputer.com/news/security/malicious-jetbrains-marketplace-plugins-steal-ai-api-keys-from-developers/


This incident analysis is provided for educational purposes. Facts are cited from the source article, while technical analysis represents professional interpretation.