Malicious Code Injection in central_wildebeest_z3n Package
Summary
MAL-2025-93490: Malicious code in central_wildebeest_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 central_wildebeest_z3n package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package is designed to manipulate developer reputation scores through the automatic generation and publication of derivative packages, which can lead to significant security risks for applications relying on it.
Vulnerability Detail
The vulnerability stems from the malicious code embedded in the central_wildebeest_z3n package, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme to inflate developer reputation scores for token rewards in the tea.xyz protocol. The ramifications include potential exposure of sensitive data, pollution of the npm registry, and the risk of dependency confusion attacks, where legitimate packages may be overshadowed by these malicious variants.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall central_wildebeest_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 central_wildebeest_z3n package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to audit your npm packages for vulnerabilities: npm audit.
Conclusion
The central_wildebeest_z3n package poses a significant security risk due to its malicious code designed to manipulate npm registry behaviors. It is essential to remove this package from your projects and monitor for any similar vulnerabilities using tools like Vulert to ensure the security of your applications.
See every vulnerability recorded for central_wildebeest_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.
The malicious code can modify your package.json file, potentially exposing sensitive data and leading to dependency confusion.
You should uninstall the central_wildebeest_z3n package immediately and check your project for any references to 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 use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.
