Malicious Code Injection in dynamic_damselfly_z3n: A Threat to npm Packages
Summary
MAL-2025-101834: Malicious code in dynamic_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 dynamic_damselfly_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 deployment of applications by providing reusable code components. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry by generating and publishing derivative packages with altered metadata.
Vulnerability Detail
The vulnerability stems from the package's involvement in a token reward campaign that floods the npm registry with malicious packages. These packages contain scripts designed to automatically modify the package.json file, removing private flags, changing version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dynamic_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 measure, avoid using the dynamic_damselfly_z3n package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your package dependencies to ensure they are secure.
Conclusion
The dynamic_damselfly_z3n package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to be vigilant and remove any affected packages from their projects. Regular updates and monitoring tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for dynamic_damselfly_z3n →
FAQ
dynamic_damselfly_z3n is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
Using the compromised package can lead to security breaches, as it modifies package metadata and can introduce malicious code into your application.
You should uninstall the dynamic_damselfly_z3n package immediately and audit your project for any other potentially compromised packages.
You can use tools like Vulert, which monitors 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 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.
