Malicious Code Detected in axserver Package - Security Alert

axserver Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15246: Malicious code in axserver (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The axserver package is an npm module designed for server-side applications, providing various functionalities for handling requests and responses. However, it has been identified to contain malicious code, posing significant security risks to applications that utilize it. This vulnerability could lead to unauthorized access, data breaches, or other malicious activities.

Vulnerability Detail

The axserver package has been found to contain malicious code that can compromise the security of applications using it. This vulnerability originated from the introduction of harmful scripts within the package, which can execute unauthorized actions on the host system. The ramifications of this vulnerability include potential data theft, system compromise, and exploitation of user data. It is crucial for developers to be aware of this issue and take immediate action to mitigate the risks associated with it.

How To Fix

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

npm uninstall axserver

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 remove the axserver package from your project until a secure version is released. Use the following command to uninstall it: npm uninstall axserver.

Conclusion

The discovery of malicious code in the axserver package poses a significant threat to applications utilizing it. Immediate action is required to update or remove the package to safeguard against potential security breaches. Developers should remain vigilant and utilize tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for axserver →

Share this vulnerability

FAQ

The axserver package is an npm module used for server-side applications, providing functionalities for handling requests and responses.

The malicious code in axserver can execute unauthorized actions on the host system, potentially leading to data breaches and system compromise.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

As a workaround, you can temporarily uninstall the axserver package using the command: npm uninstall axserver.

Detailed information about this vulnerability can be found on the GitHub page of the malicious packages project at https://github.com/ossf/malicious-packages.

How To Fix

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

npm uninstall axserver

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