Malicious Code Detected in axios-http Package

axios-http Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15238: Malicious code in axios-http (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 axios-http package is a popular HTTP client for making requests in JavaScript applications. It simplifies the process of sending asynchronous HTTP requests to REST endpoints and handling responses. However, this package has been found to contain malicious code, posing a significant risk to applications that utilize it.

Vulnerability Detail

The vulnerability in the axios-http package stems from the inclusion of malicious code that can compromise the security of applications using this package. This code can 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.

How To Fix

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

npm uninstall axios-http

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 workaround, you can remove the axios-http package from your project until a secure version is released. Use the following command to uninstall it: 'npm uninstall axios-http'. Consider using alternative packages for HTTP requests, such as axios or fetch, until the issue is resolved.

Conclusion

The discovery of malicious code in the axios-http package poses a serious threat to applications using it. It is crucial to update to a secure version or remove the package entirely to mitigate risks. Utilizing tools like Vulert can help monitor and alert for vulnerabilities in real-time.

See every vulnerability recorded for axios-http →

Share this vulnerability

FAQ

axios-http is an HTTP client for JavaScript that allows developers to make requests to REST APIs easily.

The malicious code can lead to unauthorized access and data breaches, compromising the security of your application.

You can use Vulert, which monitors open-source vulnerabilities in your software. By analyzing your package-lock.json file, it can alert you to any vulnerabilities, including this one.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

If you cannot update the package right away, consider removing it and using alternative libraries for HTTP requests until a secure version is available.

Related vulnerabilities

Recent vulnerabilities recorded for axios-http.

How To Fix

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

npm uninstall axios-http

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