Malicious Code Injection in secondary_bat_requirement Package
Summary
MAL-2025-96477: Malicious code in secondary_bat_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 secondary_bat_requirement package is part of the npm ecosystem, primarily used for managing dependencies in JavaScript applications. It is designed to facilitate the installation of various libraries and tools. However, this package has been identified as part of a malicious campaign that floods the npm registry with harmful scripts aimed at inflating developer reputation scores for token rewards. The presence of such malicious code poses significant risks to developers and their applications.
Vulnerability Detail
The vulnerability in the secondary_bat_requirement package originates from its involvement in the tea.xyz token reward campaign. This campaign utilizes autopublish scripts to generate and publish derivative packages with randomized names, effectively polluting the npm registry. The malicious payload alters the package.json file by removing private flags, changing version numbers, and continuously republishing variants. This not only compromises the integrity of the npm registry but also exposes developers to potential security risks, including the inadvertent use of compromised packages in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall secondary_bat_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 secondary_bat_requirement package and replace it with 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 secondary_bat_requirement package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor their applications for vulnerabilities. Regular updates and careful package management are essential for maintaining application security.
See every vulnerability recorded for secondary_bat_requirement →
FAQ
It is an npm package used for managing dependencies in JavaScript applications, but it has been identified as part of a malicious campaign.
The malicious code can alter your package.json file, remove private flags, and republish compromised packages, potentially leading to security vulnerabilities.
You should uninstall the secondary_bat_requirement package immediately and check for any other compromised packages in your project.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
