Malicious Code Injection in legislative_snail_requirement Package
Summary
MAL-2025-95219: Malicious code in legislative_snail_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 legislative_snail_requirement package is part of the npm ecosystem, typically used for managing dependencies in JavaScript applications. It is designed to facilitate various functionalities within applications but has been compromised by malicious actors. This package is associated with the tea.xyz token reward campaign, which has led to the proliferation of numerous derivative packages that aim to inflate developer reputation scores through deceptive practices.
Vulnerability Detail
The vulnerability in the legislative_snail_requirement package stems from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names to continuously republish variants, thereby polluting the npm registry. This not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall legislative_snail_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 legislative_snail_requirement package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The legislative_snail_requirement package poses a significant security risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised versions. It is essential for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for legislative_snail_requirement →
FAQ
It is an npm package used for managing dependencies in JavaScript applications, but it has been compromised by malicious code.
The malicious code modifies your package.json file, potentially leading to security vulnerabilities and the pollution of the npm registry.
You should uninstall the legislative_snail_requirement package immediately and look for secure alternatives.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.
Currently, there are no patches available for the legislative_snail_requirement package. The best course of action is to uninstall it and use alternative packages.
