Malicious Code Injection in harsh_damselfly_z3n Package
Summary
MAL-2025-103610: Malicious code in harsh_damselfly_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 harsh_damselfly_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. It is often utilized for various functionalities within applications, but this specific package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the tea.xyz token reward system. This campaign has led to the proliferation of numerous derivative packages with randomized names, which can compromise the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the harsh_damselfly_z3n package originates from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior allows the package to continuously republish variants, thereby polluting the npm registry. The ramifications of this vulnerability include potential exposure to malicious code, compromised application integrity, and a negative impact on the developer's reputation due to the association with these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall harsh_damselfly_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 harsh_damselfly_z3n package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file using tools like Vulert to detect any vulnerabilities in real-time.
Conclusion
The harsh_damselfly_z3n package poses a significant risk due to its malicious behavior, which can compromise application security. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities using tools like Vulert. Staying informed and proactive can help mitigate the risks associated with such vulnerabilities.
See every vulnerability recorded for harsh_damselfly_z3n →
FAQ
The harsh_damselfly_z3n package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
This vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
You should remove the harsh_damselfly_z3n package from your project and monitor for any updates or patches that may address this vulnerability.
You can use tools like Vulert, which allows you to monitor your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
