Malicious Code Injection in original_boa_0xrequest Package
Summary
MAL-2025-106792: Malicious code in original_boa_0xrequest (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 original_boa_0xrequest package is part of the npm ecosystem, often used in JavaScript applications 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 manipulate developer reputation scores through automated publishing of variants with altered metadata.
Vulnerability Detail
The vulnerability in the original_boa_0xrequest package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of applications relying on this package. The malicious payload can potentially allow unauthorized access or manipulation of the application, posing significant security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall original_boa_0xrequestIf 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 remove the original_boa_0xrequest package from your project by executing: npm uninstall original_boa_0xrequest. This will prevent any malicious code from executing while you assess alternative packages or wait for a fix.
Conclusion
The original_boa_0xrequest package poses a significant security risk due to its malicious code injection. It is essential to take immediate action by updating or removing the package to protect your application from potential threats. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.
See every vulnerability recorded for original_boa_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
The vulnerability can lead to unauthorized modifications in your application, potentially compromising its security and integrity.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
If no patched version is available, consider removing the package from your project and looking for alternative solutions.
