Critical Malicious Code Vulnerability in @asyncapi/diff Package
Summary
MAL-2025-190655: Malicious code in @asyncapi/diff (npm). Affects @asyncapi/diff versions 0.5.1 – 0.5.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/diff package is a tool designed for comparing AsyncAPI documents, allowing developers to identify differences and changes in API specifications. It is commonly used in the development of APIs to ensure consistency and accuracy in documentation. However, this package has been compromised, leading to severe security implications for any system utilizing it.
Vulnerability Detail
The vulnerability originates from malicious code embedded within the @asyncapi/diff package, specifically in versions 0.5.1 and 0.5.2. This code can fully compromise any computer that has the package installed, potentially allowing an attacker to gain control over sensitive information, including secrets and keys. The ramifications of this vulnerability are significant, as it poses a risk to the integrity and confidentiality of the systems and data of affected users.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @asyncapi/diffIf 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, you can temporarily use alternative packages for comparing AsyncAPI documents until a secure version of @asyncapi/diff is released. Consider using tools like 'diff' or other comparison libraries that do not have known vulnerabilities.
Conclusion
The @asyncapi/diff package has been found to contain malicious code that poses a significant security risk. Users are strongly advised to uninstall the package and take necessary precautions to secure their systems. Continuous monitoring for vulnerabilities using tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for @asyncapi/diff →
FAQ
You should immediately uninstall the package and rotate any sensitive information stored on the affected system.
You can use Vulert to monitor and alert for vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
Failing to address this vulnerability could lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.
No, there are currently no patched versions available for this package. The only solution is to uninstall it.
It is advisable to wait for a secure version to be released before using the package again. Always monitor for updates and security advisories.
