Malicious Code Injection in vivacious_magpie_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-110598: Malicious code in vivacious_magpie_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
vivacious_magpie_z3n is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. The package's functionality is compromised by malicious scripts that manipulate its metadata and behavior.
Vulnerability Detail
The vulnerability in vivacious_magpie_z3n originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry, potentially affecting other developers and projects relying on npm packages. The scripts involved are designed to continuously republish variants, exacerbating the issue.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall vivacious_magpie_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 remove the vivacious_magpie_z3n package from your project by executing: npm uninstall vivacious_magpie_z3n. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The vivacious_magpie_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 take immediate action by updating or removing the package to safeguard their projects. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for vivacious_magpie_z3n →
FAQ
vivacious_magpie_z3n is an npm package involved in a token reward campaign that automates the generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry, affecting the integrity of packages and potentially introducing malicious code into your project.
You should update the package to the latest version or remove it from your project until a secure version is released.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can also check your application for vulnerabilities using the Vulert playground.
Regularly audit your dependencies, keep them updated, and use tools like Vulert to monitor for vulnerabilities in real-time.
