Malicious Code Vulnerability in administrative_monkey_z3n Package
Summary
MAL-2025-99196: Malicious code in administrative_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
Background
The administrative_monkey_z3n package is part of the npm ecosystem, often utilized for various JavaScript applications. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to manipulate its own metadata and publish variants to inflate developer reputation scores, posing significant risks to users and the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability originates from the package being associated with the tea.xyz token reward campaign, which employs scripts that automatically generate and publish derivative packages with randomized names. The malicious payload alters the package.json file by removing private flags, changing version numbers, and continuously republishing variants. This behavior can lead to pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially introducing security risks into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall administrative_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, avoid using the administrative_monkey_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly monitor your package-lock.json file for any unauthorized changes or additions.
Conclusion
The administrative_monkey_z3n package poses a significant risk due to its malicious behavior of altering package metadata and flooding the npm registry with derivative packages. It is crucial for developers to remove this package from their projects and monitor for any related vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for administrative_monkey_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the publication of derivative packages.
The vulnerability can lead to the pollution of the npm registry, making it harder to find legitimate packages and potentially introducing security risks into your application.
You should uninstall the administrative_monkey_z3n package immediately and check for any dependencies that may rely on it.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.
