Which versions of @3stripes/components are malicious?

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

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

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

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

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

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

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

Malicious package

@3stripes/componentsnpm

Advisory published Apr 16, 2026Updated Sep 1, 2026

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

MAL-2026-2703

Immediate action

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

npm uninstall @3stripes/components

What this malware does

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

Malicious versions

3 flagged

999.0.0999.0.2999.0.3

Indicators of compromise (SHA-256)

e1802b435f525fc58053a5fb484836310d00485ae4cf2d49ce307cace50a249c

31ba4725ff03b9b0a4645734fca9af46fbd145e147f7fb7ee0942853c425f53f

03ed2196a7fd5e6118f009805ae3980689c92b505876eaddb0ab91da568e00ec

Detection & response playbook

Malicious package

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

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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