Malicious Code Detected in @x-clients/features: Version 3.1.10 Vulnerability

@x-clients/features Updated 03 Feb 2026

Summary

03/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-703: Malicious code in @x-clients/features (npm). Affects @x-clients/features versions 3.1.10. 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 package '@x-clients/features' is a JavaScript library available through npm, designed to provide various features for client applications. It is widely used in web development for enhancing user interfaces and functionalities. However, version 3.1.10 has been flagged for containing malicious code that compromises the security of applications utilizing it.

Vulnerability Detail

The vulnerability in '@x-clients/features' version 3.1.10 stems from its communication with a domain linked to malicious activities. Additionally, the package executes commands that are associated with harmful behavior, potentially leading to unauthorized access, data breaches, or system compromise. This issue was identified by the OpenSSF Package Analysis project, which monitors and evaluates the safety of open-source packages.

How To Fix

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

npm uninstall @x-clients/features

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 remove the '@x-clients/features' package from your project until a secure version is released. This can be done using the command: 'npm uninstall @x-clients/features'. Alternatively, consider using a different package that provides similar functionality without the security risks.

Conclusion

The '@x-clients/features' package version 3.1.10 has been identified as malicious, posing significant security risks to applications that utilize it. Users are advised to update to a secure version or remove the package until a fix is available. Utilizing tools like Vulert can help monitor and manage open-source vulnerabilities effectively.

See every vulnerability recorded for @x-clients/features →

Share this vulnerability

FAQ

The package communicates with a domain known for malicious activities and executes harmful commands, which can compromise application security.

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

If an immediate update is not possible, consider removing the package or using an alternative until a secure version is available.

Regularly check for updates to your dependencies and consider using tools like Vulert to monitor vulnerabilities in real-time.

Using older versions may expose your application to known vulnerabilities. It is best to use the latest secure version or find an alternative.

How To Fix

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

npm uninstall @x-clients/features

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