Critical Malicious Code Vulnerability in require-in-package Package
Summary
MAL-2026-1529: Malicious code in require-in-package (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 require-in-package package is a Node.js utility that allows developers to manage package dependencies effectively. It is commonly used in various applications to streamline the inclusion of other packages. However, this package has been identified as containing malicious code, posing significant security risks to any system utilizing it.
Vulnerability Detail
The vulnerability stems from the presence of embedded malicious code within the require-in-package package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code means that it can lead to full control of the affected system by an outside entity, making it imperative for users to take immediate action to secure their environments.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall require-in-packageIf 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 isolate the affected application from the internet and limit access to sensitive data until the package is removed and the system is secured. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The require-in-package package poses a significant security risk due to the embedded malicious code. Immediate action is required to remove the package and secure any compromised systems. Users are encouraged to utilize tools like Vulert for ongoing monitoring of their dependencies.
See every vulnerability recorded for require-in-package →
FAQ
You should immediately remove the require-in-package package from your system and rotate any secrets or keys stored on that computer.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any signup.
Currently, there is no patched version available. The best course of action is to remove the package entirely.
Failing to address this vulnerability can lead to unauthorized access to sensitive information and potential control of your system by malicious actors.
While many packages are safe, it is essential to regularly monitor and audit your dependencies for vulnerabilities using tools like Vulert.
