Malicious Code Injection in crude_ape_z3n Package - npm Vulnerability
Summary
MAL-2025-101107: Malicious code in crude_ape_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 crude_ape_z3n package is part of the npm ecosystem, primarily used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign associated with the tea.xyz token reward system. This package is designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in the crude_ape_z3n package stems from its malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these tainted packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall crude_ape_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 crude_ape_z3n package and look for alternative packages that provide similar functionalities without the associated risks. Additionally, you can monitor your project for any unexpected changes in the package.json file.
Conclusion
The crude_ape_z3n package poses a significant security risk due to its malicious code designed to manipulate npm registry integrity. It is crucial for developers to remove this package and monitor their projects for any unauthorized changes. Utilizing tools like Vulert can help in maintaining the security of your applications.
See every vulnerability recorded for crude_ape_z3n →
FAQ
The crude_ape_z3n package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.
This vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
You should uninstall the crude_ape_z3n package immediately using 'npm uninstall crude_ape_z3n' and monitor your project for any unauthorized changes.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on the latest security advisories related to the packages you use.
