What does the @x-clients/features malware do?

The package @x-clients/features was found to contain malicious code. The OpenSSF Package Analysis project identified '@x-clients/features' @ 3.1.10 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of @x-clients/features are malicious?

The following npm versions of @x-clients/features are flagged malicious: 3.1.10. Treat any of these as compromised.

How do I remediate @x-clients/features if I installed it?

Remove @x-clients/features from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @x-clients/features — how do I know if it already compromised me?

If @x-clients/features was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find @x-clients/features across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @x-clients/features (version 3.1.10).

Malicious package

@x-clients/featuresnpm

Advisory published Feb 3, 2026Updated Feb 6, 2026

@x-clients/features is a confirmed malicious npm package (MAL-2026-703) that executes malicious code on install (malicious version 3.1.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @x-clients/features (npm)

MAL-2026-703

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @x-clients/features

What this malware does

The package @x-clients/features was found to contain malicious code.

The OpenSSF Package Analysis project identified '@x-clients/features' @ 3.1.10 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

3.1.10

Indicators of compromise (SHA-256)

7951ad31a71a40e5342af07a4a221d31eecd39faacf00adc2a2b899f1e5b3616

11011581541d17f28bb84a9e3ea5703dfc0f4834506875fa48f61ea79c87c30c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @x-clients/features (version 3.1.10).
If you installed it — respond
Remove @x-clients/features from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @x-clients/features was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @x-clients/features on npm has been identified as a malicious package (version 3.1.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @x-clients/features-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database