Malicious Code Injection in Systematic Capybara Requirement Package
Summary
MAL-2025-96920: Malicious code in systematic_capybara_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 'systematic_capybara_requirement' package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant security risks.
Vulnerability Detail
The vulnerability originates from the package being associated with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of dependent projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall systematic_capybara_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 prevent the installation of this package by using npm's package-lock.json to lock your dependencies. Additionally, consider using the following command to uninstall the package if it is already installed: 'npm uninstall systematic_capybara_requirement'.
Conclusion
The 'systematic_capybara_requirement' package poses a significant security risk due to its association with malicious publishing practices. It is essential to take immediate action to remove or update the package to safeguard your project from potential threats.
See every vulnerability recorded for systematic_capybara_requirement →
FAQ
The malicious code can lead to unauthorized modifications in your project's dependencies, potentially compromising security and stability.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If an immediate update is not possible, consider removing the package and monitoring your application for any unusual behavior.
Yes, tools like Vulert can monitor your package-lock.json for open-source vulnerabilities in real-time.
Using compromised packages can lead to data breaches, loss of user trust, and potential legal ramifications depending on the nature of the data involved.
