Which versions of @3stripes/core are malicious?

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

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

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

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

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

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

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

Malicious package

@3stripes/corenpm

Advisory published Apr 16, 2026Updated Sep 1, 2026

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

MAL-2026-2705

Immediate action

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

npm uninstall @3stripes/core

What this malware does

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

Malicious versions

3 flagged

999.0.0999.0.2999.0.3

Indicators of compromise (SHA-256)

89789a8eeb080b72500b1022b24fe6cf711304a906618502cce7257adb0530f7

af3a9f22040b78bb5d4973940dff6f5acad0f3a338e26c8f025ca96245acacc9

e5007499cbca571166a3e3a1952d92bb12deae262d63a7eddca831d0de964495

Detection & response playbook

Malicious package

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

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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