Malicious Code Injection in exuberant_wasp_z3n Package
Summary
MAL-2025-94412: Malicious code in exuberant_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 exuberant_wasp_z3n package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the tea.xyz token reward system. This package is particularly vulnerable due to its inclusion in a series of autopublish scripts that automate the generation and publication of derivative packages.
Vulnerability Detail
The vulnerability originates from the malicious design of the exuberant_wasp_z3n package, 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 compromising the integrity of the ecosystem and affecting developers' reputations.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall exuberant_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, you can avoid using the exuberant_wasp_z3n package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity of packages before installation.
Conclusion
The exuberant_wasp_z3n package poses a significant risk due to its malicious code designed to manipulate npm registry entries. It is essential to remove this package from your projects and utilize secure alternatives to maintain the integrity of your applications.
See every vulnerability recorded for exuberant_wasp_z3n →
FAQ
The malicious code can lead to the pollution of the npm registry, affecting the reputation of developers and potentially introducing security risks into applications that depend on this package.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Simply upload your package-lock.json file to the Vulert playground at Vulert Scanner to check for vulnerabilities.
No, there is no patch available for this package. The recommended action is to uninstall it and replace it with a secure alternative.
You should immediately uninstall the exuberant_wasp_z3n package and review your project's dependencies for any other potentially malicious packages.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from trusted sources.
