Malicious Code Injection in Alleged Primate Requirement Package
Summary
MAL-2025-93196: Malicious code in alleged_primate_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 'alleged_primate_requirement' package is part of the npm ecosystem, typically used for managing dependencies in JavaScript applications. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package compromises its integrity and poses significant risks to developers and their applications.
Vulnerability Detail
The vulnerability originates from the package being associated with the tea.xyz token reward campaign, which floods the npm registry with malicious packages. It contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the pollution of the npm registry and can potentially compromise the security of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall alleged_primate_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 workaround, you can temporarily avoid using the 'alleged_primate_requirement' package by removing it from your dependencies. You can do this by executing the following command in your terminal: npm uninstall alleged_primate_requirement.
Conclusion
The 'alleged_primate_requirement' package poses a significant security risk due to its malicious code designed to manipulate package metadata and flood the npm registry. It is crucial for developers to remove this package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can help in identifying such risks in real-time.
See every vulnerability recorded for alleged_primate_requirement →
FAQ
The package contains malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.
If you have installed the 'alleged_primate_requirement' package, you should uninstall it immediately and monitor your application for any unusual behavior.
Yes, the vulnerability can lead to the pollution of the npm registry and compromise the security of applications that depend on the affected package.
As of now, there is no specific patch for the 'alleged_primate_requirement' package. The best course of action is to remove the package from your project.
