Malicious Code Vulnerability in active_grasshopper_requirement Package
Summary
MAL-2025-93112: Malicious code in active_grasshopper_requirement (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The active_grasshopper_requirement package is part of the npm ecosystem, often utilized in JavaScript applications for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is particularly vulnerable due to its association with autopublish scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign linked to the tea.xyz token reward system. The malicious code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This results in the continuous republishing of these variants, which pollutes the npm registry and can lead to reputation inflation for developers involved in the campaign. The ramifications include potential security risks for applications relying on this package, as well as the degradation of the npm ecosystem's integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall active_grasshopper_requirementIf 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 workaround, you can avoid using the active_grasshopper_requirement package altogether. If it is already in use, consider replacing it with a trusted alternative that does not exhibit malicious behavior.
Conclusion
The active_grasshopper_requirement package poses a significant security risk due to its malicious code that alters package metadata. It is crucial for developers to remove this package and monitor their applications for vulnerabilities to maintain the integrity of their software.
See every vulnerability recorded for active_grasshopper_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The vulnerability can lead to security risks and may compromise the integrity of your application by introducing malicious code.
You should remove the active_grasshopper_requirement package and consider using a trusted alternative.
Currently, there is no patched version available. It is best to remove the package until a fix is released.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
