Critical Malicious Code Vulnerability in xeno-code Package

xeno-code Updated 02 Oct 2025

Summary

16/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5990: Malicious code in xeno-code (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The xeno-code package is an npm library designed for various coding utilities and enhancements. It is widely used in JavaScript projects for its ease of integration and functionality. However, it has been identified to contain malicious code that poses severe security risks to any system where it is installed.

Vulnerability Detail

The vulnerability originates from the inclusion of embedded malicious code within the xeno-code package. This code can compromise the integrity of the host system, allowing unauthorized access to sensitive information such as secrets and keys. The presence of this malicious code means that any computer running this package should be considered fully compromised, leading to potential data breaches and loss of control over the system.

How To Fix

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

npm uninstall xeno-code

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

Currently, the only effective workaround is to uninstall the xeno-code package entirely. You can do this by running the following command in your terminal: npm uninstall xeno-code.

Conclusion

The xeno-code package has been identified to contain malicious code that poses significant security risks. Immediate action is required to uninstall the package and secure any sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for xeno-code →

Share this vulnerability

FAQ

You should uninstall the xeno-code package immediately and rotate any sensitive information stored on the affected system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

As of now, there is no patched version available. The best course of action is to uninstall the package.

Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

Vulert monitors and alerts you in real-time for open-source vulnerabilities using just the package-lock.json file, ensuring you stay informed about potential risks.

How To Fix

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

npm uninstall xeno-code

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