Malicious Code Injection in horrible_partridge_requirement: A Threat to npm Packages
Summary
MAL-2025-94867: Malicious code in horrible_partridge_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 package 'horrible_partridge_requirement' is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior poses a significant risk to the integrity of the npm registry and the security of applications relying on these packages.
Vulnerability Detail
The vulnerability in 'horrible_partridge_requirement' stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This not only pollutes the npm registry but also compromises the security of applications that may unknowingly depend on these tainted packages. The origin of this vulnerability is linked to a broader campaign aimed at exploiting npm for token rewards, making it a significant concern for developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall horrible_partridge_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 'horrible_partridge_requirement' package and replace it with a trusted alternative. Additionally, you can use the following command to uninstall the package: npm uninstall horrible_partridge_requirement.
Conclusion
The 'horrible_partridge_requirement' package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.
See every vulnerability recorded for horrible_partridge_requirement →
FAQ
It is an npm package associated with a malicious campaign that aims to inflate developer reputation scores by publishing derivative packages.
The malicious code can compromise your application's integrity by introducing unwanted behavior and polluting the npm registry.
You should uninstall the package immediately and monitor your application for any unusual behavior.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.
