Which versions of @3stripes/sdk are malicious?

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

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

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

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

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

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

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

Malicious package

@3stripes/sdknpm

Advisory published Apr 16, 2026Updated Sep 1, 2026

@3stripes/sdk is a confirmed malicious npm package (MAL-2026-2706) 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/sdk (npm)

MAL-2026-2706

Immediate action

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

npm uninstall @3stripes/sdk

What this malware does

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

Malicious versions

3 flagged

999.0.0999.0.2999.0.3

Indicators of compromise (SHA-256)

666e919ccd693b12794a86ef277db76a4c2ed717a00f44f00a6543f018b5676e

78177fb122038c79210d2b2a9b477a78c4d918bfc9819382745e541503a7e8ea

d6ea94a6ab350235023cb2a89c8e8f894aa00b583bdb905787364b5a6b497adb

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @3stripes/sdk (3 malicious versions).
If you installed it — respond
Remove @3stripes/sdk 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/sdk 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/sdk 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-01844RLUA-2026-05781

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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