Malicious Code Injection in maximum_wasp_z3n Package - npm Vulnerability
Summary
MAL-2025-98809: Malicious code in maximum_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 maximum_wasp_z3n package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package, like many others, is intended to facilitate the development of applications by providing reusable code components. However, it has been identified as part of a malicious campaign that exploits npm's package management system, leading to potential security risks for developers and their applications.
Vulnerability Detail
The vulnerability in the maximum_wasp_z3n package stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file, removing private flags and changing version numbers. The malicious payload is designed to generate random package names and continuously republish variants, which can lead to pollution of the npm registry and compromise the integrity of the development environment. This vulnerability poses significant risks, including the potential for unauthorized access to sensitive data and the degradation of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall maximum_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 measure, you can prevent the installation of the maximum_wasp_z3n package by using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include this package by checking your package.json and removing any references to it.
Conclusion
The maximum_wasp_z3n package poses a significant security risk due to its malicious code injection capabilities. It is crucial for developers to be aware of this vulnerability and take immediate action to remove the affected package from their projects. Regular monitoring and updates are essential to maintain a secure development environment.
See every vulnerability recorded for maximum_wasp_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to flood the npm registry with derivative packages.
The vulnerability can lead to unauthorized modifications of your package.json file and the potential introduction of malicious code into your application.
You should uninstall the maximum_wasp_z3n package immediately using the command 'npm uninstall maximum_wasp_z3n'.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
