Critical Malicious Code Vulnerability in node-native-bridge Package
Summary
MAL-2026-965: Malicious code in node-native-bridge (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The node-native-bridge package is a Node.js library that facilitates the interaction between JavaScript and native code. It is commonly used in applications that require performance optimizations or access to system-level resources. However, this package has been found to contain malicious code, posing a significant risk to any system that has it installed.
Vulnerability Detail
The vulnerability originates from the presence of embedded malicious code within the node-native-bridge package. This code can compromise any computer running the package, allowing unauthorized access to sensitive information such as secrets and keys. The implications are severe, as it can lead to complete control of the affected system by an external entity. Users are advised to treat any system with this package as fully compromised.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall node-native-bridgeIf 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
There are no effective workarounds for this vulnerability. The only recommended action is to uninstall the node-native-bridge package and secure your system.
Conclusion
The node-native-bridge package has been identified as containing malicious code, leading to severe security risks for any system using it. Immediate action is required to remove the package and secure sensitive information. Users are encouraged to utilize tools like Vulert to monitor for vulnerabilities in their applications.
See every vulnerability recorded for node-native-bridge →
FAQ
You should immediately remove the package and rotate any sensitive information stored on the affected system.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Keeping this package installed poses a significant risk of unauthorized access to your system and sensitive data.
There are no effective mitigations; the best course of action is to uninstall the package entirely.
While removing the package is essential, there is no guarantee that all malicious software has been removed. It is advisable to perform a thorough security audit.
References
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
