Which versions of @3stripes/shared are malicious?

The following npm versions of @3stripes/shared are flagged malicious: 999.0.0, 999.0.2, 999.0.3. Treat any of these as compromised.

How do I remediate @3stripes/shared if I installed it?

Remove @3stripes/shared 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 @3stripes/shared — how do I know if it already compromised me?

If @3stripes/shared 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 @3stripes/shared part of a known attack campaign?

Yes — @3stripes/shared is associated with the RLMA-2026-01845, RLUA-2026-05782 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 @3stripes/shared across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @3stripes/shared (3 malicious versions).

Part of a larger attack: @3stripes published 13 malicious packages. See the full campaign →

Malicious package

@3stripes/sharednpm

Advisory published Apr 16, 2026Updated Sep 1, 2026

@3stripes/shared is a confirmed malicious npm package (MAL-2026-2707) that executes malicious code on install (malicious versions 999.0.0, 999.0.2, 999.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @3stripes/shared (npm)

MAL-2026-2707

Immediate action

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

npm uninstall @3stripes/shared

What this malware does

The package @3stripes/shared was found to contain malicious code.

Malicious versions

3 flagged

999.0.0999.0.2999.0.3

Indicators of compromise (SHA-256)

0fe8866473feacdaa679c0085b19c4356aea0d0c2f0762196713cc31f8c3f3df

3ca39203b484afe25fca27596d3c3c81a0a6765ad88d3b129871375127bdb5ea

5f9a796350af1f4523deaf0249b67b2cac099a1bc7bca3f5f9fdb9424a07da75

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01845RLUA-2026-05782

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @3stripes/shared-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