Malicious Code Injection in required_grasshopper_z3n Package
Summary
MAL-2025-96314: Malicious code in required_grasshopper_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 required_grasshopper_z3n package is part of the npm ecosystem, often used in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, leading to potential security risks for users.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the required_grasshopper_z3n package, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only pollutes the npm registry but also poses a risk of unintentional dependency on compromised packages, which can lead to further exploitation and security breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall required_grasshopper_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 avoid using the required_grasshopper_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The required_grasshopper_z3n package poses significant security risks due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant about the packages they use and to take immediate action to remove any affected packages. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in real-time.
See every vulnerability recorded for required_grasshopper_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. Check your application by visiting the Vulert playground at Vulert Scanner.
Using this package can lead to dependency on malicious code, which may compromise your application's security and integrity.
Regularly audit your dependencies, use tools like npm audit, and stay informed about known vulnerabilities in the packages you use.
Immediately uninstall the package and review your project's dependencies for any potential risks. Consider using alternative packages.
