Critical Malicious Code Vulnerability in @asyncapi/studio Package

@asyncapi/studio Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190863: Malicious code in @asyncapi/studio (npm). Affects @asyncapi/studio versions 0.20.1 – 1.0.3. 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/studio package is a tool designed for creating and managing AsyncAPI documents, which are used to describe asynchronous APIs. It provides features for visualizing and editing API specifications, making it easier for developers to work with event-driven architectures. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users who have it installed.

Vulnerability Detail

The vulnerability stems from the discovery of embedded malicious code within the @asyncapi/studio package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The malicious code was identified through sources like Amazon Inspector and GHSA malware reports, indicating that users should treat any system running this package as fully compromised. Immediate action is required to mitigate the risks associated with this vulnerability.

How To Fix

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

npm uninstall @asyncapi/studio

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

As a workaround, users should rotate all secrets and keys stored on the affected computer from a different, secure machine. This is crucial as the malicious code may have already compromised sensitive data.

Conclusion

The @asyncapi/studio package has been found to contain malicious code that poses serious security risks. Users are advised to uninstall the package immediately and take steps to secure their sensitive information. Monitoring tools like Vulert can help in identifying and managing such vulnerabilities effectively.

See every vulnerability recorded for @asyncapi/studio →

Share this vulnerability

FAQ

Immediately uninstall 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.

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

Failure to address this vulnerability could lead to unauthorized access to sensitive data and complete compromise of your system.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated.

How To Fix

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

npm uninstall @asyncapi/studio

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