Critical Malicious Code Vulnerability in battleaxe Package

battleaxe Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15516: Malicious code in battleaxe (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 battleaxe package is an npm library designed for various functionalities within JavaScript applications. It is utilized for its ease of integration and utility in enhancing application features. However, this package has been identified to contain malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the battleaxe package originates from the inclusion of malicious code that can compromise the security of applications using this library. This code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The vulnerability is present from version 0 and is classified as a serious threat due to its potential impact on application integrity and user data safety.

How To Fix

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

npm uninstall battleaxe

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, consider replacing the battleaxe package with an alternative library that offers similar functionality without the associated risks. Ensure to review the security of any new package before integration.

Conclusion

The battleaxe package has been identified as containing malicious code, posing significant risks to applications that utilize it. Users are advised to uninstall the package immediately and monitor for updates or alternatives. Utilizing tools like Vulert can help in identifying vulnerabilities in your software.

See every vulnerability recorded for battleaxe →

Share this vulnerability

FAQ

The battleaxe package is an npm library used in JavaScript applications for various functionalities, but it has been found to contain malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application by visiting the Vulert playground at Vulert Scanner.

Immediately uninstall the battleaxe package using 'npm uninstall battleaxe' and look for a secure alternative.

Using the battleaxe package can lead to unauthorized access, data breaches, and other harmful actions within your application.

Currently, there is no patch available for the battleaxe package. It is recommended to uninstall it until a secure version is released.

How To Fix

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

npm uninstall battleaxe

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