Malicious Code Detected in asynd Package - Security Alert

asynd Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14996: Malicious code in asynd (npm). Affected versions are not published. 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 asynd package is a Node.js library designed for asynchronous programming, providing utilities for managing asynchronous operations. It is commonly used in various applications to enhance performance and streamline code execution. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the asynd package originates from the inclusion of malicious code that can compromise the security of applications utilizing this library. This malicious code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue is particularly concerning as it affects all versions starting from the initial release, making it imperative for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall asynd

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 temporary workaround, users can remove the asynd package from their project until a secure version is released. This can be done by executing the following command: 'npm uninstall asynd'. Alternatively, consider using other asynchronous libraries that do not have known vulnerabilities.

Conclusion

The discovery of malicious code in the asynd package highlights the importance of maintaining secure coding practices and regularly updating dependencies. Users are urged to take immediate action to protect their applications from potential threats by updating or removing the affected package.

See every vulnerability recorded for asynd →

Share this vulnerability

FAQ

The asynd package is a Node.js library used for managing asynchronous programming, providing utilities to streamline asynchronous operations.

The malicious code in the asynd package can lead to unauthorized access and potential data breaches, posing serious security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.

If you cannot update the package right away, consider uninstalling it and using alternative libraries that provide similar functionality without known vulnerabilities.

Regularly check for updates to your packages and consider using tools like Vulert to monitor your dependencies for vulnerabilities.

How To Fix

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

npm uninstall asynd

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