Which versions of @3stripes/config are malicious?

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

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

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

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

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

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

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

Malicious package

@3stripes/confignpm

Advisory published Apr 16, 2026Updated Sep 1, 2026

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

MAL-2026-2704

Immediate action

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

npm uninstall @3stripes/config

What this malware does

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

Malicious versions

3 flagged

999.0.0999.0.2999.0.3

Indicators of compromise (SHA-256)

881041b766be20c6615053f24bff772ebe453068659d26f4143cfa0ff4118bd5

9fea72a3f12c815ec03d587d20386eb4726c301d381fa23d720c25dc903bdcb4

1fdbc221d428a99c8ce0e229b041247a7e9ecc18e0a0459588c07f63112fba5b

Detection & response playbook

Malicious package

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

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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