Critical Malicious Code Vulnerability in @asyncapi/multi-parser Package

@asyncapi/multi-parser Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190661: Malicious code in @asyncapi/multi-parser (npm). Affects @asyncapi/multi-parser versions 2.2.1 – 2.2.2. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The @asyncapi/multi-parser package is an npm library designed to facilitate the parsing of AsyncAPI documents. It is widely used in applications that require the integration of APIs, enabling developers to work with API specifications efficiently. However, this package has been compromised, leading to significant security concerns.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the @asyncapi/multi-parser package. This code can fully compromise any computer that has the package installed or running, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code has been confirmed by security researchers, and it poses a severe risk to users and their systems.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @asyncapi/multi-parser

If 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 available for this vulnerability. The best course of action is to remove the package entirely and ensure that your system is secure.

Conclusion

The @asyncapi/multi-parser package has been identified as containing malicious code that poses a significant security risk. Users are advised to uninstall the package immediately and take necessary precautions to secure their systems. Regular monitoring for vulnerabilities using tools like Vulert can help prevent such issues in the future.

See every vulnerability recorded for @asyncapi/multi-parser →

Share this vulnerability

FAQ

You should uninstall the package immediately and rotate any sensitive information stored on your system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.

No, there are currently no patched versions available for this package. The only solution is to remove it.

Failing to address this vulnerability can lead to unauthorized access to sensitive data and potential control over your system by malicious actors.

Vulert monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file, providing an easy way to stay informed.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @asyncapi/multi-parser

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback