Critical Malicious Code Vulnerability in @asyncapi/specs Package

@asyncapi/specs Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190643: Malicious code in @asyncapi/specs (npm). Affects @asyncapi/specs versions 6.10.1 – 6.9.1. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The @asyncapi/specs package is a library used in the JavaScript ecosystem, specifically within the npm package manager, to define and manage AsyncAPI specifications. It is designed to facilitate the development of event-driven APIs by providing a structured format for documentation. 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 stems from malicious code embedded within the @asyncapi/specs package, identified under the alias GHSA-5jj9-3vg7-7785. 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 vulnerability is linked to the package's distribution through npm, where it was found that versions 6.8.2, 6.8.3, 6.9.1, and 6.10.1 are affected. 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/specs

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

Currently, the only effective workaround is to uninstall the affected package and rotate any sensitive credentials stored on the compromised system. There are no alternative packages recommended at this time.

Conclusion

The discovery of malicious code in the @asyncapi/specs package poses a significant risk to users and their systems. Immediate action is required to uninstall the affected versions and secure any exposed credentials. Monitoring tools like Vulert can assist in identifying vulnerabilities in your applications.

See every vulnerability recorded for @asyncapi/specs →

Share this vulnerability

FAQ

Immediately uninstall the package and rotate any secrets or keys that may have been compromised.

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.

The affected versions include 6.8.2, 6.8.3, 6.9.1, and 6.10.1.

Currently, there is no patched version available. Users should uninstall the package until a secure version is released.

Failing to address this vulnerability can lead to unauthorized access to sensitive information and complete system compromise.

How To Fix

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

npm uninstall @asyncapi/specs

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