Malicious Code Injection in metropolitan_damselfly_z3n Package
Summary
MAL-2025-105809: Malicious code in metropolitan_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
Background
The metropolitan_damselfly_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability stems from malicious code embedded within the metropolitan_damselfly_z3n package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The primary goal of this malicious payload is to continuously republish variants of the package, thereby polluting the npm registry and potentially harming developers who rely on legitimate packages. The origin of this issue is linked to a broader campaign that exploits npm for token rewards, making it a significant concern for developers and users alike.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall metropolitan_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 metropolitan_damselfly_z3n package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The metropolitan_damselfly_z3n package contains malicious code that poses a significant risk to developers and users within the npm ecosystem. It is crucial to take immediate action by updating or removing the package and to monitor your projects for vulnerabilities using tools like Vulert.
See every vulnerability recorded for metropolitan_damselfly_z3n →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.
The malicious code modifies your package.json file, removes private flags, and can lead to the pollution of the npm registry, potentially affecting your project's dependencies.
You should immediately update the package to the latest version or remove it from your project to mitigate any risks.
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 needing to sign up.
