Critical Malicious Code Vulnerability in @baanx/common Package
Summary
MAL-2026-16485: Malicious code in @baanx/common (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 @baanx/common package is a library used in Node.js applications, typically for common functionalities shared across various modules. It is designed to streamline development by providing reusable code components. However, this package has been identified to contain malicious code, posing significant security risks to any application that utilizes it.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the @baanx/common package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The implications of this vulnerability are severe, as it can lead to complete control of the affected system by an external entity. Users are advised to treat any system running this package as fully compromised.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @baanx/commonIf 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 other than removing the package entirely. Ensure that your application does not rely on @baanx/common for any critical functionality.
Conclusion
The @baanx/common package has been identified as containing malicious code that poses a significant security threat. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert to monitor for vulnerabilities in their applications.
See every vulnerability recorded for @baanx/common →
FAQ
You should immediately uninstall the package and rotate any sensitive information stored on the affected system.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
No, there is currently no patched version available for this package. The only solution is to remove it.
Failure to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential exploitation by malicious actors.
It is highly discouraged to use @baanx/common due to the inherent risks. It is best to find alternative packages that provide similar functionality without the security risks.
