Critical Malicious Code Vulnerability in axio.js Package

axio.js Updated 02 Oct 2025

Summary

15/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5895: Malicious code in axio.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 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 axio.js package is a widely used JavaScript library in the npm ecosystem, designed for making HTTP requests from Node.js and the browser. It simplifies the process of sending asynchronous requests and handling responses, making it a popular choice among developers for API interactions. However, this package has been identified to contain malicious code, posing significant security risks to systems that utilize it.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the axio.js package. This code can compromise any computer that has the package installed, leading to unauthorized access and control by external entities. The ramifications include potential data breaches, loss of sensitive information, and the risk of further malware installation. The vulnerability is classified under CWE-506, indicating that the product contains code that appears to be malicious in nature.

How To Fix

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

npm uninstall axio.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

As a temporary measure, you can avoid using the axio.js package and replace it with alternative libraries such as Axios or Fetch API for making HTTP requests. This will help mitigate the risks associated with the malicious code until a fix is implemented.

Conclusion

The axio.js package has been identified to contain malicious code, posing significant security risks to users. Immediate action is required to remove the package and consider alternatives. Monitoring tools like Vulert can help keep your projects secure by alerting you to vulnerabilities.

See every vulnerability recorded for axio.js →

Share this vulnerability

FAQ

axio.js is a JavaScript library used for making HTTP requests in web applications, simplifying the process of interacting with APIs.

The malicious code can compromise your system, allowing unauthorized access and control, which may lead to data breaches and further malware installation.

You should immediately remove the axio.js package from your project and consider updating to a patched version if available.

Yes, you can use libraries like Axios or the Fetch API as alternatives for making HTTP requests.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing the package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.

How To Fix

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

npm uninstall axio.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