Malicious Code Injection in few_wildebeest_z3n Package
Summary
MAL-2025-94497: Malicious code in few_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 few_wildebeest_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores in exchange for token rewards. 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 leads to the continuous republishing of variants that pollute the npm registry, potentially affecting other developers and users who rely on the integrity of npm packages. The malicious scripts included in the package are designed to automate these actions, making it difficult for users to detect the underlying issue.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall few_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 few_wildebeest_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unexpected changes or additions that may indicate the presence of malicious packages.
Conclusion
The few_wildebeest_z3n package has been identified as containing malicious code that compromises its integrity and the security of the npm registry. It is crucial for developers to remove this package from their projects and monitor for any updates or patches. Utilizing tools like Vulert can help in identifying vulnerabilities in real-time.
See every vulnerability recorded for few_wildebeest_z3n →
FAQ
The few_wildebeest_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The vulnerability can compromise the integrity of your project by introducing malicious code that modifies package configurations and floods the npm registry with unwanted packages.
You should immediately remove the few_wildebeest_z3n package from your project and monitor for any updates or patches that may address the vulnerability.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
