Malicious Code Injection in linear_beaver_requirement Package
Summary
MAL-2025-95260: Malicious code in linear_beaver_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 linear_beaver_requirement package is part of the npm ecosystem, often used for various JavaScript applications. It is designed to facilitate certain functionalities within the npm framework. However, this package has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation and publication of derivative packages. This vulnerability poses a significant risk to developers and users relying on this package.
Vulnerability Detail
The vulnerability originates from the package being associated with a token reward campaign that floods the npm registry with malicious packages. These packages contain 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 compromise the integrity of applications relying on this package. The malicious payload can potentially expose users to security risks and degrade the overall quality of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall linear_beaver_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 linear_beaver_requirement package until a secure version is released. Additionally, you can monitor your package dependencies using tools like Vulert, which allows you to check for vulnerabilities in your application without requiring code access or installation. You can use the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability.
Conclusion
The linear_beaver_requirement package has been identified as containing malicious code that can compromise the integrity of applications using it. It is crucial for developers to take immediate action by updating or removing the package to mitigate potential risks. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities effectively.
See every vulnerability recorded for linear_beaver_requirement →
FAQ
It is an npm package used in JavaScript applications, but it has been identified as part of a malicious campaign.
The vulnerability can lead to the pollution of the npm registry and may expose your application to security risks.
You should update the package to a patched version or remove it from your project until a secure version is available.
You can use tools like Vulert to monitor and alert in real-time for open-source vulnerabilities in your software.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.
