Malicious Code Injection in alive_grasshopper_z3n Package
Summary
MAL-2025-93191: Malicious code in alive_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 alive_grasshopper_z3n package is part of the npm ecosystem, often utilized in various JavaScript applications. This package has been identified as part of a larger malicious campaign associated with the tea.xyz token reward system. It is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names.
Vulnerability Detail
The vulnerability in the alive_grasshopper_z3n package stems from its malicious code, 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, polluting the npm registry and potentially compromising the integrity of applications that depend on this package. The origin of this vulnerability is linked to a campaign that exploits npm's publishing mechanisms to manipulate package visibility and reputation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall alive_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 workaround, you can remove the alive_grasshopper_z3n package from your project by executing the following command: npm uninstall alive_grasshopper_z3n. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The alive_grasshopper_z3n package contains malicious code that poses significant risks to applications using it. It is essential to update or remove this package to safeguard your project from potential exploitation. Utilizing tools like Vulert can help in monitoring and managing such vulnerabilities effectively.
See every vulnerability recorded for alive_grasshopper_z3n →
FAQ
The malicious code can lead to unauthorized modifications of your project's package.json, potentially exposing your application to further vulnerabilities and affecting its integrity.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By uploading your package-lock.json file, you can quickly assess if your application is impacted.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and avoid using unverified packages from the npm registry.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risks.
Detailed information about this vulnerability can be found in the official npm registry and security advisories related to the alive_grasshopper_z3n package.
