Malicious Code Injection in specific_dragon_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-96704: Malicious code in specific_dragon_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The specific_dragon_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to potential security risks for developers and users alike.
Vulnerability Detail
The vulnerability in specific_dragon_z3n originates from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to automatically generate and publish variants with randomized names, effectively polluting the registry. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, which can inflate developer reputation scores fraudulently. This poses significant risks, including the potential for dependency confusion, unauthorized access to sensitive data, and the introduction of further vulnerabilities into dependent projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall specific_dragon_z3nIf it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a temporary workaround, you can avoid using the specific_dragon_z3n package and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The specific_dragon_z3n package poses a significant security risk due to its association with a malicious npm campaign. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for specific_dragon_z3n →
FAQ
specific_dragon_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising security and functionality.
You should remove the specific_dragon_z3n package from your project immediately and monitor for any updates or patches.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
