Malicious Code Injection in Scary Monkey Z3N: A Threat to npm Ecosystem
Summary
MAL-2025-108416: Malicious code in scary_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
Scary Monkey Z3N is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the distribution of token rewards through the npm ecosystem. However, it has been identified as containing malicious code that compromises its integrity and the security 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 is intended to inflate developer reputation scores for token rewards, leading to pollution of the npm registry with derivative packages. The ramifications include potential security risks for developers using this package, as well as a degradation of the npm ecosystem's reliability.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall scary_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 remove the Scary Monkey Z3N package from your project by running: npm uninstall scary_monkey_z3n. This will prevent any malicious code from executing until a patched version is available.
Conclusion
The Scary Monkey Z3N package has been identified as containing malicious code that poses a significant risk to the npm ecosystem. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.
See every vulnerability recorded for scary_monkey_z3n →
FAQ
The malicious code modifies package.json files to remove private flags and generates random package names, which can lead to the proliferation of untrustworthy packages in the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By simply analyzing your package-lock.json file, you can identify if your application is affected.
Using this package can expose your application to security vulnerabilities, as it may introduce untrusted code and affect the integrity of your project.
Regularly audit your dependencies and utilize tools like Vulert to monitor for vulnerabilities in your open-source packages.
If an immediate update is not possible, consider removing the package from your project until a secure version is released.
