Malicious Code Injection in Inappropriate Louse Requirement Package
Summary
MAL-2025-94975: Malicious code in inappropriate_louse_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 'inappropriate_louse_requirement' package is part of a broader campaign associated with the tea.xyz token reward initiative. This package, like many others in this campaign, is designed to manipulate npm's package registry by generating and publishing numerous derivative packages. Its primary function is to inflate developer reputation scores for token rewards, but it has been compromised to include malicious scripts that can harm developers and users alike.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the 'inappropriate_louse_requirement' package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names, which can lead to the pollution of the npm registry. The malicious payload can also create a significant security risk by allowing unauthorized access to sensitive information and potentially compromising the integrity of applications that rely on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall inappropriate_louse_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 'inappropriate_louse_requirement' package altogether. If it is already part of your project, consider removing it and replacing it with a trusted alternative package that serves a similar purpose.
Conclusion
The 'inappropriate_louse_requirement' package poses a significant security risk due to its malicious code designed to manipulate npm's package registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to ensure the integrity and security of their applications.
See every vulnerability recorded for inappropriate_louse_requirement →
FAQ
It is a package associated with the tea.xyz token reward campaign, designed to manipulate npm's registry for reputation inflation.
The malicious code can modify your package.json file, remove private flags, and publish unauthorized packages, potentially compromising your application's security.
You should remove the 'inappropriate_louse_requirement' package from your project and monitor for any updates or patches.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
