Which versions of @3stripes/toolkit are malicious?

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

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

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

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

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

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

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

Malicious package

@3stripes/toolkitnpm

Advisory published Apr 16, 2026Updated Sep 1, 2026

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

MAL-2026-2708

Immediate action

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

npm uninstall @3stripes/toolkit

What this malware does

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

Malicious versions

3 flagged

999.0.0999.0.2999.0.3

Indicators of compromise (SHA-256)

3e688987c305e8fd68079e8f717275d092f2266c4e8c7bc81fdaa0c8a20726d0

4529c8ef3e0953799338bc7e0cc7d6ce4f1d8797b3e0984d362ebd26df6bec1c

589171bc18c8d2af3cf42f45b34cedbfa1020fd69be9a5742c967f892e883672

Detection & response playbook

Malicious package

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

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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