Critical Malicious Code Vulnerability in @asyncapi/bundler Package
Summary
MAL-2025-190652: Malicious code in @asyncapi/bundler (npm). Affects @asyncapi/bundler versions 0.6.5 – 0.6.6. 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 @asyncapi/bundler package is a tool designed for bundling AsyncAPI documents, facilitating the development of APIs by providing a structured way to describe and document them. It is widely used in the JavaScript ecosystem, particularly for projects that rely on npm packages. However, recent findings have revealed that certain versions of this package contain embedded malicious code, posing significant security risks to users and their systems.
Vulnerability Detail
The vulnerability originates from malicious code embedded within the @asyncapi/bundler package, specifically in versions 0.6.5 and 0.6.6. This code can compromise any computer that has the package installed, potentially 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 external entities. Users are advised to treat any system with this package installed as fully compromised.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @asyncapi/bundlerIf 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 specific workarounds to mitigate the risks posed by this vulnerability other than removing the affected package. Users should ensure that they do not run any applications that depend on the compromised versions until they have been fully removed.
Conclusion
The discovery of malicious code in the @asyncapi/bundler package highlights the importance of vigilance in managing open-source dependencies. Users must act swiftly to remove affected versions and secure their systems to prevent potential exploitation.
See every vulnerability recorded for @asyncapi/bundler →
FAQ
You should immediately remove the package and rotate any sensitive information stored on your 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.
Versions 0.6.5 and 0.6.6 of the @asyncapi/bundler package are known to contain the malicious code.
While other versions may not be affected, it is advisable to stay updated with the latest releases and monitor for any further vulnerabilities.
Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.
