Malicious Activity Detected in @xene/core Package - Vulnerability MAL-2025-6069

@xene/core Updated 02 Oct 2025

Summary

20/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6069: Malicious code in @xene/core (npm). Affects @xene/core versions 0.4.1. 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 @xene/core package is a component of the npm ecosystem, designed to facilitate various functionalities in JavaScript applications. It is widely used for its performance and ease of integration. However, this package has been identified to communicate with a domain associated with malicious activities, raising significant security concerns for users and developers relying on it.

Vulnerability Detail

The vulnerability identified as MAL-2025-6069 stems from the @xene/core package's communication with a domain linked to malicious activities. This could potentially lead to data breaches, unauthorized access, or the execution of harmful code within applications utilizing this package. The risk is particularly pronounced for applications that handle sensitive data or are deployed in production environments.

How To Fix

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

npm uninstall @xene/core

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 an immediate workaround, consider removing the @xene/core package from your project until a secure version is confirmed. You can do this by executing the command: 'npm uninstall @xene/core'. Additionally, monitor your application for any unusual behavior that may indicate exploitation of this vulnerability.

Conclusion

The @xene/core package has been flagged for a serious vulnerability due to its communication with a malicious domain. It is crucial for developers and users to take immediate action by updating or removing the package to safeguard their applications from potential threats.

See every vulnerability recorded for @xene/core →

Share this vulnerability

FAQ

The vulnerability involves the package communicating with a domain associated with malicious activities, posing risks to application security.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

If an immediate update is not feasible, consider removing the package and monitoring your application for any suspicious activities.

While specific exploits have not been detailed, the communication with a malicious domain indicates a high risk of potential exploitation.

How To Fix

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

npm uninstall @xene/core

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