Malicious Code Injection in productive_wasp_z3n Package
Summary
MAL-2025-96043: Malicious code in productive_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 productive_wasp_z3n package is part of the npm ecosystem, commonly used for various JavaScript applications. It has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the generation of derivative packages. This package is particularly vulnerable due to its association with scripts that automate the publishing of malicious variants.
Vulnerability Detail
The vulnerability in the productive_wasp_z3n package stems from its involvement in a token reward campaign that floods the npm registry with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names, leading to pollution of the npm registry. The malicious payload can compromise the integrity of applications relying on this package, potentially leading to unauthorized access or execution of harmful code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall productive_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 remove the productive_wasp_z3n package from your project by executing: npm uninstall productive_wasp_z3n. This will prevent the execution of any malicious code associated with it until a secure version is available.
Conclusion
The productive_wasp_z3n package has been identified as containing malicious code that can compromise applications using it. It is crucial to take immediate action by updating or removing the package to protect your software from potential threats.
See every vulnerability recorded for productive_wasp_z3n →
FAQ
The productive_wasp_z3n package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automated publishing of derivative packages.
This vulnerability can lead to the modification of your package.json file, potentially allowing unauthorized code execution and compromising the integrity of your application.
If you are using the productive_wasp_z3n package, you should immediately update it to the latest version or remove it from your project to mitigate the risk.
Yes, you can use Vulert to monitor and alert in real-time for open-source vulnerabilities in your software. It requires only your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
