Malicious Code Vulnerability in experimental_mandrill_z3n Package
Summary
MAL-2025-102394: Malicious code in experimental_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
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 experimental_mandrill_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 can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants that pollute the npm registry, potentially affecting other developers and users by creating confusion and undermining trust in the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall experimental_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 experimental_mandrill_z3n package from your project by executing: npm uninstall experimental_mandrill_z3n. This will prevent any malicious code from executing while you assess the situation and look for a secure alternative package.
Conclusion
The experimental_mandrill_z3n package has been identified as containing malicious code that poses a significant risk to developers and the npm ecosystem. It is crucial to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for experimental_mandrill_z3n →
FAQ
The vulnerability involves malicious code that modifies package.json files and republishes variants to pollute the npm registry.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software without requiring code access.
It is advisable to uninstall the package immediately and check for any updates or patches that may address the vulnerability.
Yes, the malicious behavior can lead to confusion among developers and users, as well as potential security risks from untrusted packages.
You can use Vulert's playground to check if your application is affected by this vulnerability by analyzing your package-lock.json file.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
