Malicious Code Detected in axoeyob Package - MAL-2025-15244

axoeyob Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15244: Malicious code in axoeyob (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 axoeyob package is an npm module that is used for various functionalities within JavaScript applications. It is designed to provide developers with tools to enhance their applications. However, this package has been identified as containing malicious code, which poses significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the axoeyob package stems from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code can lead to unauthorized access, data breaches, or other malicious activities that can severely impact the integrity and confidentiality of user data. The vulnerability 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 axoeyob

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 replace the axoeyob package with an alternative package that provides similar functionality without the associated risks. Ensure that you thoroughly review the alternative package's security and functionality before implementation.

Conclusion

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

See every vulnerability recorded for axoeyob →

Share this vulnerability

FAQ

The axoeyob package is an npm module used in JavaScript applications for various functionalities.

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

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

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

You should uninstall the axoeyob package immediately and consider using an alternative package that does not have known vulnerabilities.

How To Fix

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

npm uninstall axoeyob

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