Critical Malicious Code Vulnerability in @asyncapi/parser Package
Summary
MAL-2025-190640: Malicious code in @asyncapi/parser (npm). Affects @asyncapi/parser versions 3.4.1 – 3.4.2. 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/parser package is a tool designed for parsing AsyncAPI documents, which are used to describe APIs in a machine-readable format. This package is widely utilized in the development of applications that rely on asynchronous communication. However, it has been found to contain malicious code that compromises the security of any system where it is installed.
Vulnerability Detail
The vulnerability stems from the presence of embedded malicious code within the @asyncapi/parser package, specifically in versions 3.4.1 and 3.4.2. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this malicious code is linked to a security incident reported in the GitHub Security Advisory (GHSA-wjmr-9cr8-3wgj). 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/parserIf 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 to mitigate the risks posed by this vulnerability. The best course of action is to remove the package entirely and ensure that all sensitive information is secured.
Conclusion
The discovery of malicious code in the @asyncapi/parser package poses a significant security risk to users. Immediate action is required to remove the package and secure any sensitive information. Users should stay informed about updates and patches for this package to ensure their systems remain secure.
See every vulnerability recorded for @asyncapi/parser →
FAQ
You should immediately remove the package and rotate any secrets or keys stored on your system.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Currently, there is no patched version available. Users are advised to remove the package until a safe version is released.
Failure to address this vulnerability can lead to unauthorized access to sensitive information and complete system compromise.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
