Malicious Code Injection in brainy_tern_requirement Package
Summary
MAL-2025-93421: Malicious code in brainy_tern_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 brainy_tern_requirement package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security concerns.
Vulnerability Detail
The vulnerability originates from the brainy_tern_requirement package being associated with the tea.xyz token reward campaign. This campaign has led to the creation of numerous malicious packages that contain scripts designed to automatically publish derivative packages with altered metadata. The malicious payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names, which can lead to the pollution of the npm registry and potential exploitation of developers' reputations.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall brainy_tern_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 brainy_tern_requirement package and look for 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 brainy_tern_requirement package poses a significant security risk due to its association with malicious activities in the npm ecosystem. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the integrity of your applications.
See every vulnerability recorded for brainy_tern_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to the pollution of the npm registry and may compromise your application's integrity by introducing malicious code.
You should uninstall the brainy_tern_requirement package immediately using the command: npm uninstall brainy_tern_requirement.
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 requiring any signup.
