Malicious Code Injection in diverse_mandrill_z3n: A Threat to npm Packages
Summary
MAL-2025-94077: Malicious code in diverse_mandrill_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 package 'diverse_mandrill_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's repository by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'diverse_mandrill_z3n' originates from its association with the tea.xyz token reward campaign. The malicious code embedded within this package modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these tainted packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall diverse_mandrill_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 'diverse_mandrill_z3n' package from your project by executing the command: 'npm uninstall diverse_mandrill_z3n'. This will prevent any malicious code from executing in your environment until a fix is applied.
Conclusion
The 'diverse_mandrill_z3n' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to stay vigilant, update their packages regularly, and utilize tools like Vulert to monitor for vulnerabilities in their applications.
See every vulnerability recorded for diverse_mandrill_z3n →
FAQ
The vulnerability involves malicious code that modifies package.json and floods the npm registry with derivative packages.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.
Using this package can lead to security breaches, as it may introduce malicious code into your application.
Yes, tools like Vulert can monitor your package-lock.json file to alert you in real-time for any open-source vulnerabilities.
If an immediate update is not possible, consider uninstalling the package as a temporary measure to mitigate risks.
