Malicious Code Injection in Ethical Gazelle Requirement Package
Summary
MAL-2025-94301: Malicious code in ethical_gazelle_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
Background
The 'ethical_gazelle_requirement' package is part of the npm ecosystem, often utilized in various JavaScript applications. It is designed to facilitate specific functionalities within projects. However, this package has been identified as part of a malicious campaign that aims to manipulate the npm registry by generating and publishing derivative packages with altered metadata.
Vulnerability Detail
This vulnerability originates from a malicious payload embedded within the 'ethical_gazelle_requirement' package. It modifies the package.json file to remove private flags, alters version numbers, and creates random package names, leading to the pollution of the npm registry. The malicious scripts are designed to inflate developer reputation scores through the automatic generation of numerous derivative packages, which can severely impact the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ethical_gazelle_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 temporary workaround, you can remove the 'ethical_gazelle_requirement' package from your project by executing the command: 'npm uninstall ethical_gazelle_requirement'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The 'ethical_gazelle_requirement' package has been identified as containing malicious code that poses significant risks to the npm ecosystem. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.
See every vulnerability recorded for ethical_gazelle_requirement →
FAQ
The vulnerability involves malicious code that modifies package metadata and generates numerous derivative packages, compromising the npm registry.
You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any signup.
The impacts include the pollution of the npm registry, potential reputation damage for developers, and risks associated with using compromised packages.
You should check the package repository for any available patches and update to the latest secure version of the package.
If immediate updates are not possible, consider uninstalling the package to mitigate risks until a secure version is released.
