Malicious Code Injection in grotesque_lemur_requirement Package
Summary
MAL-2025-94759: Malicious code in grotesque_lemur_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 grotesque_lemur_requirement package is part of the npm ecosystem, often used in JavaScript applications for various functionalities. However, it has been identified as part of a malicious campaign that seeks to exploit npm's package management system. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the grotesque_lemur_requirement package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The primary risk is that it can lead to the pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially compromising the integrity of their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall grotesque_lemur_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 avoid using the grotesque_lemur_requirement package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The grotesque_lemur_requirement package poses a significant risk due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is crucial for developers to remove this package and monitor their projects for any vulnerabilities to maintain application integrity.
See every vulnerability recorded for grotesque_lemur_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your application's integrity and security.
You should remove the grotesque_lemur_requirement package from your project and monitor for any unauthorized changes in your package-lock.json file.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
