Malicious Code Detected in aasync Package - Security Alert

aasync Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-13941: Malicious code in aasync (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 aasync package is a Node.js library designed for asynchronous programming, allowing developers to manage asynchronous operations more efficiently. It is widely used in various applications for its simplicity and effectiveness. However, recent findings have revealed that the package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the aasync package stems from the inclusion of malicious code that can compromise the integrity of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall aasync

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 measure, users can remove the aasync package from their project until a secure version is released. This can be done by running the following command: npm uninstall aasync. Consider using alternative libraries that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the aasync 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 posed by this vulnerability.

See every vulnerability recorded for aasync →

Share this vulnerability

FAQ

aasync is a Node.js library that facilitates asynchronous programming, allowing developers to handle asynchronous operations more effectively.

The malicious code found in aasync can potentially lead to unauthorized access and data breaches in applications that utilize this package.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

If immediate updates are not possible, consider uninstalling the aasync package and using alternative libraries until a secure version is available.

Vulert monitors and alerts users in real-time for open-source vulnerabilities using just the package-lock.json file, ensuring that developers are informed of potential risks.

Related vulnerabilities

Recent vulnerabilities recorded for aasync.

How To Fix

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

npm uninstall aasync

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