What is the recent Cursor AI IDE extension supply chain attack that resulted in $500,000 crypto theft?
A sophisticated cyberattack in June 2025 involved hackers weaponizing a malicious “Solidity Language” extension in Cursor AI IDE, allowing them to steal $500,000 in cryptocurrency assets from a blockchain developer. The attackers used search ranking manipulation to position their fake extension above legitimate ones, deploying multi-stage malware through remote access tools like ScreenConnect. This incident highlights the rising threat of supply chain attacks targeting AI development environments and emphasizes the need for vigilant extension verification, endpoint monitoring, and proactive cybersecurity measures.
Quick answer: A weaponized extension for the Cursor AI IDE, spread through the Open VSX registry, let attackers steal about $500,000 in cryptocurrency from a Russian blockchain developer. The attackers pushed their package up the search results so it looked genuine. Check the publisher, download count and name before installing any extension.
Key takeaways
- The extension was distributed through Open VSX, a registry Cursor uses instead of Microsoft's Marketplace.
- Check the publisher, install count and recent updates before installing any editor extension.
- Keep crypto wallet keys off machines used for general development.
Table of Contents
- What Happened in the Cursor AI IDE Extension Attack?
- Why Is This Attack Concerning for Cybersecurity Teams?
- How the Infection Chain Worked, Step-by-Step
- Attack Infrastructure: More Than One Package Involved
- How Hackers Manipulated the Open VSX Search Algorithm
- What Tools and Techniques Were Involved?
- What Are the Lessons for Developers and Security Professionals?
- Conclusion
In July 2025, cybersecurity researchers uncovered a sophisticated cyberattack where hackers stole $500,000 in cryptocurrency assets from a Russian blockchain developer. The attack method? A weaponized IDE extension targeting the increasingly popular Cursor AI IDE. This case highlights how supply chain attacks are evolving, using platforms like Open VSX and developer tools to infiltrate even highly cautious users.
What Happened in the Cursor AI IDE Extension Attack?
A Russian developer, despite practicing strict cybersecurity hygiene, became the victim of a malicious package disguised as a Solidity syntax highlighting extension for the Cursor AI IDE.
The fake extension, named "Solidity Language," was downloaded over 54,000 times before being detected and removed. The attackers cleverly manipulated search rankings, pushing their extension above legitimate ones by updating it frequently and maintaining high download numbers.
Timeline of the Attack:
-
June 15, 2025: Malicious extension last updated, ranked 4th in search results.
-
June 2025: Victim installs the extension, unknowingly allowing the attack.
-
July 2025: Investigation reveals malware campaign connected with multiple other malicious packages.
Why Is This Attack Concerning for Cybersecurity Teams?
Unlike traditional phishing or malware, this attack weaponized:
-
Open-source software ecosystems.
-
AI-assisted development platforms.
-
Supply chain manipulation via search ranking algorithms.
Even vigilant developers are vulnerable if malicious extensions are positioned above legitimate ones in search results.
How the Infection Chain Worked, Step-by-Step
The attackers engineered a multi-layered infection process. Here’s how it unfolded:
| Stage | Action Performed |
|---|---|
| Initial Contact | Malicious extension contacts C2 server angelic[.]su. |
| PowerShell Script | Retrieves 1.txt script checking for ScreenConnect presence. |
| Conditional Payload | If ScreenConnect absent, downloads 2.txt script triggering installer. |
| Remote Access Setup | Installs legitimate ScreenConnect software communicating with relay.lmfao[.]su. |
| Persistence | Attackers gain remote access blending into normal system operations. |
Attack Infrastructure: More Than One Package Involved
The forensic investigation found multiple related malicious packages:
-
solsafe (npm repository)
-
solaibot (VS Code extension)
-
among-eth (VS Code extension)
-
blankebesxstnion (VS Code extension)
All shared the same command-and-control (C2) infrastructure.
How Hackers Manipulated the Open VSX Search Algorithm
The attackers used SEO-like tactics within the IDE ecosystem:
-
Frequent Updates: To appear “recently maintained.”
-
Artificial Download Counts: Building trust and better visibility.
-
Strategic Naming: Mimicking official extensions.
Example search result screenshot from Securelist showed the malicious extension ranking 4th while the authentic one was only 8th.
What Tools and Techniques Were Involved?
| Technique | Purpose |
|---|---|
| Supply Chain Attack | Compromising trust in software distribution channels |
| Social Engineering | Masking malicious intent as legitimate developer tools |
| Remote Access Software Misuse | Blending malicious activity with legitimate admin tools |
| PowerShell Script Chaining | Multi-stage payload delivery and evasion |
What Are the Lessons for Developers and Security Professionals?
If You’re a Developer:
-
Always verify extensions manually.
-
Prefer official sources over third-party registries.
-
Monitor unusual system activity post-installation.
For Organizations:
-
Implement extension whitelisting.
-
Use Endpoint Detection and Response (EDR) tools.
-
Train development teams on modern supply chain attack vectors.
Conclusion: Supply Chain Threats in AI-Enhanced Development
This $500,000 crypto heist via the Cursor AI IDE shows how supply chain attacks are moving beyond npm, PyPI, and classic open-source registries.
AI development tools, once considered niche, are now prime targets for cybercriminals.
Organizations must prioritize supply chain security as part of their overall incident response and cloud security posture.
To take this further with guided labs and an instructor, see our cyber security programme with live labs.
Related reading
Frequently Asked Questions
What's Your Reaction?
Like
0
Dislike
0
Love
0
Funny
0
Wow
0
Sad
0
Angry
0