Malicious Code Injection in robust_wasp_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-108181: Malicious code in robust_wasp_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 package robust_wasp_z3n is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses significant risks to developers who may inadvertently use these compromised packages.
Vulnerability Detail
The vulnerability in robust_wasp_z3n stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior allows the package to continuously republish variants, polluting the npm registry and potentially leading to security issues for developers who rely on these packages. The origin of this vulnerability is linked to the broader trend of malicious packages flooding the npm ecosystem, specifically targeting the tea protocol token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall robust_wasp_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, avoid using the robust_wasp_z3n package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your dependencies to ensure they are secure.
Conclusion
The robust_wasp_z3n package poses a significant risk due to its malicious behavior, which can compromise the integrity of your npm projects. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain a secure development environment.
See every vulnerability recorded for robust_wasp_z3n →
FAQ
robust_wasp_z3n is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising security and functionality.
You should uninstall the package immediately using the command: npm uninstall robust_wasp_z3n, and replace it with a secure alternative.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file.
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.
