Which versions of sheinx are malicious?

The following npm versions of sheinx are flagged malicious: 999.0.101, 999.0.102, 999.0.103. Treat any of these as compromised.

How do I remediate sheinx if I installed it?

Remove sheinx 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 sheinx — how do I know if it already compromised me?

If sheinx 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.

Is sheinx part of a known attack campaign?

Yes — sheinx is associated with the RLMA-2026-01565 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find sheinx across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for sheinx (3 malicious versions).

Malicious package

sheinxnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

sheinx is a confirmed malicious npm package (MAL-2026-1842) that executes malicious code on install (malicious versions 999.0.101, 999.0.102, 999.0.103). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sheinx (npm)

MAL-2026-1842

Immediate action

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

npm uninstall sheinx

What this malware does

The package sheinx was found to contain malicious code.

Malicious versions

3 flagged

999.0.101999.0.102999.0.103

Indicators of compromise (SHA-256)

1d83d2ff6ca4660dcd86da6d6c0c58b48c3e0b3a7b0be6645c37988b2e582916

491bd46d3cc55fb18d3343ede29a51034a964051c1fd6a6ad8cf709fe18fac83

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for sheinx (3 malicious versions).
If you installed it — respond
Remove sheinx 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 sheinx 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. sheinx on npm has been identified as a malicious package (versions 999.0.101, 999.0.102, 999.0.103 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01565

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks sheinx-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