Critical Vulnerability in asyync Package

asyync Updated 02 Oct 2025

Summary

02/09/2020
CRITICAL
No i
Critical
9.8

GHSA-rm7c-x424-g2mw: Malicious Package in asyync. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The asyync package is an npm package used for asynchronous programming in Node.js applications. It provides various utility functions to handle asynchronous operations. However, all versions of asyync were found to be typosquatting a popular package with a similar name. This malicious package tracked users who installed it and uploaded information to a remote server. The uploaded data included the name of the downloaded package, the intended package name, the Node version, and whether the process was running with sudo privileges. It is important to remove this package from your dependencies and ensure correct package names are used during installation.

Vulnerability Detail

The vulnerability in the asyync package arises from its typosquatting behavior. By masquerading as a legitimate package, it tricks users into installing it instead of the intended package. Once installed, the malicious package collects sensitive information and sends it to a remote server. The potential ramifications of this vulnerability include the compromise of user data, unauthorized access to systems, and potential misuse of sudo privileges. The severity of this vulnerability is rated as CRITICAL with a CVSS score of 9.8.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Conclusion

The asyync package has been found to be typosquatting a popular package, collecting sensitive information, and sending it to a remote server. This vulnerability poses a significant risk to user data and system security. It is crucial to remove the malicious package and exercise caution when installing dependencies. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for asyync →

Share this vulnerability

FAQ

The asyync package is used for asynchronous programming in Node.js applications. It provides utility functions to handle asynchronous operations and improve code readability.

The typosquatting attack involves creating a package with a similar name to a popular package. Users who accidentally mistype the package name during installation end up installing the malicious package instead of the intended one.

The malicious package collects the name of the downloaded package, the intended package name, the Node version, and whether the process is running with sudo privileges. This information is then sent to a remote server.

The potential consequences include the compromise of user data, unauthorized access to systems, and potential misuse of sudo privileges. It is crucial to remove the malicious package and ensure correct package names are used.

To protect your project, always double-check the package names before installing any dependencies. Pay attention to any slight variations or misspellings that could indicate a typosquatting attempt.

Related vulnerabilities

Recent vulnerabilities recorded for asyync.

How To Fix

No fixed version is published for this vulnerability.

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