Malicious Package in asycn - Remote Code Execution

asycn Updated 02 Oct 2025

Summary

02/09/2020
CRITICAL
No i
Critical
9.8

GHSA-h26f-j4mv-84g7: Malicious Package in asycn. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The asycn package is an npm package used for asynchronous programming in Node.js applications. It provides utilities and functions to handle asynchronous operations. However, all versions of the asycn package were found to contain a malicious package that was 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 information included the name of the downloaded package, the name of the intended package, the Node.js version, and whether the process was running with sudo privileges. The package did not compromise the system further.

Vulnerability Detail

The vulnerability in the asycn package allowed for remote code execution due to the inclusion of the malicious package. By installing the incorrect package, users unknowingly exposed their systems to potential attacks. The malicious package tracked user information and sent it to a remote server, which could lead to privacy breaches and unauthorized access. 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 asycn package contained a malicious package that typosquatted a popular package, compromising user privacy and potentially exposing systems to unauthorized access. To mitigate this vulnerability, remove the package from your dependencies and ensure correct package names during installation. Regularly updating packages and staying informed about security advisories is crucial. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for asycn →

Share this vulnerability

FAQ

The asycn package is used for asynchronous programming in Node.js applications. It provides utilities and functions to handle asynchronous operations, making it easier to write asynchronous code.

The malicious package in asycn typosquatted a popular package and tracked users who installed it. It uploaded information to a remote server, including the name of the downloaded package, the name of the intended package, the Node.js version, and whether the process was running with sudo privileges. However, there is no evidence of further compromise beyond the data collection.

The potential ramifications of this vulnerability include privacy breaches, unauthorized access, and potential misuse of the collected information. Attackers could use the gathered data to target specific systems or exploit vulnerabilities in other components of the system.

To mitigate the risk of typosquatting attacks, always double-check the package names before installation. Pay attention to the spelling and ensure that you are installing the intended package. Verifying the package's popularity, maintainer reputation, and reading user reviews can also help identify potential typosquatting attempts.

If you have installed the malicious asycn package, it is recommended to remove it immediately from your dependencies. Additionally, consider monitoring your system for any suspicious activities and take appropriate actions to secure your environment.

Related vulnerabilities

Recent vulnerabilities recorded for asycn.

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