Malicious Code Injection in warm_monkey_z3n: A Threat to npm Packages
Summary
MAL-2025-97313: Malicious code in warm_monkey_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 package warm_monkey_z3n is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in warm_monkey_z3n originates from its association with a malicious campaign that utilizes autopublish scripts to generate and publish derivative packages with altered metadata. The malicious payload modifies the package.json file by removing private flags, changing version numbers, and creating random package names. This behavior not only pollutes the npm registry but also compromises the integrity of the packages, potentially leading to security risks for applications that depend on them.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall warm_monkey_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 warm_monkey_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package-lock.json file is monitored for any changes using tools like Vulert.
Conclusion
The warm_monkey_z3n package poses a significant security risk due to its malicious code injection capabilities. It is crucial for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert to ensure the integrity and security of their applications.
See every vulnerability recorded for warm_monkey_z3n →
FAQ
warm_monkey_z3n is an npm package that has been identified as part of a malicious campaign aimed at manipulating package metadata and inflating developer reputation scores.
The vulnerability can lead to the inclusion of malicious code in your application, compromising its security and potentially exposing sensitive data.
You should uninstall the package immediately using the command 'npm uninstall warm_monkey_z3n' and monitor your project for any other affected packages.
Yes, tools like Vulert can monitor your package-lock.json file for vulnerabilities in real-time, alerting you to any issues without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
