Malicious Code Injection in appalling_sole_requirement Package
Summary
MAL-2025-93248: Malicious code in appalling_sole_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 appalling_sole_requirement package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation of numerous derivative packages. The package is designed to automate the generation and publication of these derivative packages, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability originates from the appalling_sole_requirement package being part of a malicious campaign associated with the tea.xyz token reward initiative. It includes scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of trust in the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall appalling_sole_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 measure, you can avoid using the appalling_sole_requirement package and any of its derivatives. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The appalling_sole_requirement package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is essential to remove this package from your projects and utilize monitoring tools like Vulert to stay informed about potential vulnerabilities. By taking these steps, you can help safeguard your applications and maintain the integrity of your development environment.
See every vulnerability recorded for appalling_sole_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 the inclusion of malicious code in your project, compromising its security and integrity.
You should remove the appalling_sole_requirement package from your project immediately and monitor for any other affected packages.
Using tools like Vulert can help monitor your project for vulnerabilities in real-time, allowing you to take action quickly.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
