Critical Malicious Code Vulnerability in @asyncapi/cli Package
Summary
MAL-2025-190653: Malicious code in @asyncapi/cli (npm). Affects @asyncapi/cli versions 4.1.2 – 4.1.3. 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/cli package is a command-line interface tool designed for working with AsyncAPI specifications, enabling developers to generate documentation, code, and other resources from AsyncAPI files. It is widely used in the development of APIs, providing essential functionalities for managing and interacting with API specifications. However, recent findings have revealed that certain versions of this package contain malicious code that compromises the security of any system where it is installed.
Vulnerability Detail
The vulnerability originates from malicious code embedded within the @asyncapi/cli package, specifically in versions 4.1.2 and 4.1.3. This code can fully 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 may lead to data breaches and loss of control over the affected systems. Users are advised to treat any system with this package as compromised and take immediate action.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @asyncapi/cliIf 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 effects of this vulnerability other than removing the package and rotating any compromised secrets. It is advisable to monitor your systems for any unusual activity following the removal.
Conclusion
The discovery of malicious code in the @asyncapi/cli package poses a significant threat to users and their systems. Immediate action is required to mitigate the risks associated with this vulnerability. Users should uninstall the affected package and rotate any sensitive information. Continuous monitoring for vulnerabilities is essential to maintain the security of your applications.
See every vulnerability recorded for @asyncapi/cli →
FAQ
Immediately uninstall the package using npm uninstall @asyncapi/cli 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 without needing to sign up.
The risks include unauthorized access to sensitive data, potential data breaches, and loss of control over the affected systems.
Currently, there are no patched versions available. It is recommended to avoid using this package until a secure version is released.
Vulert provides a solution to monitor and alert for open-source vulnerabilities in your software using just the package-lock.json file.
