Critical Malicious Code Vulnerability in asios.js Package

asios.js Updated 02 Oct 2025

Summary

15/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5894: Malicious code in asios.js (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The asios.js package is a JavaScript library available through the npm ecosystem, designed for making HTTP requests. It is often used in web applications to facilitate communication with APIs. However, this package has been identified to contain malicious code that compromises the security of any system where it is installed, making it a significant risk for developers and organizations relying on it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the asios.js package. This code can lead to full system compromise, allowing unauthorized access to sensitive information such as secrets and keys stored on the affected machine. The malicious nature of this code has been confirmed through various sources, indicating that any system running this package should be considered at risk. The vulnerability is categorized under CWE-506, which highlights the danger of embedded malicious code.

How To Fix

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

npm uninstall asios.js

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

Currently, the best workaround is to uninstall the asios.js package from your project. You can do this by running the following command in your terminal: npm uninstall asios.js. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The asios.js package poses a serious security threat due to embedded malicious code. Immediate action is required to remove the package and secure any compromised systems. Regular monitoring and using tools like Vulert can help prevent future vulnerabilities.

See every vulnerability recorded for asios.js →

Share this vulnerability

FAQ

Immediately uninstall the asios.js package and rotate any secrets or keys stored on the affected machine.

You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

As of now, there is no patched version available. It is recommended to remove the package entirely.

Failing to address this vulnerability could result in unauthorized access to sensitive data and complete control of your system by malicious actors.

While many npm packages are safe, it is essential to review their code and monitor for vulnerabilities regularly. Tools like Vulert can help with this.

How To Fix

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

npm uninstall asios.js

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