Malicious Code Injection in Roasted Wildebeest Z3N Package
Summary
MAL-2025-108176: Malicious code in roasted_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 'roasted_wildebeest_z3n' package is part of the npm ecosystem, typically used for various JavaScript applications. It has been identified as part of a malicious campaign that aims to exploit npm's package publishing system. This package is associated with the tea.xyz token reward initiative, which has been linked to the automatic generation and publication of derivative packages to inflate developer reputation scores.
Vulnerability Detail
The vulnerability originates from the package being designed to include autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall roasted_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 measure, you can avoid using the 'roasted_wildebeest_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any dependencies that may have been affected by this malicious package.
Conclusion
The 'roasted_wildebeest_z3n' package poses a significant risk due to its malicious code injection capabilities. It is crucial for developers to be aware of this vulnerability, remove the affected package, and consider using alternative solutions. Regular monitoring of dependencies is essential to ensure the security of applications.
See every vulnerability recorded for roasted_wildebeest_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security.
You should remove the package from your project and monitor for any updates or patches that may address the issue.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
Vulert is a tool that uses package-lock.json to monitor and alert for open-source vulnerabilities in your software, helping you maintain secure applications.
