Which versions of @3stripes/lib are malicious?

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

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

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

If @3stripes/lib 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.

How do I find @3stripes/lib across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @3stripes/lib (version 999.0.2).

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

Malicious package

@3stripes/libnpm

Advisory published Mar 15, 2026Updated Mar 23, 2026

@3stripes/lib is a confirmed malicious npm package (MAL-2026-1428) that executes malicious code on install (malicious version 999.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @3stripes/lib (npm)

MAL-2026-1428

Immediate action

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

npm uninstall @3stripes/lib

What this malware does

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

The OpenSSF Package Analysis project identified '@3stripes/lib' @ 999.0.2 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

999.0.2

Indicators of compromise (SHA-256)

2254316d2b62e5297bf8b2f78453a4e10ab018b4db69ca8c8b3b961048a769a1

2cefc88878b1d12a39232d39387d16e564c71a9ce50047e025e7f26f848d4858

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @3stripes/lib (version 999.0.2).
If you installed it — respond
Remove @3stripes/lib 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/lib 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/lib on npm has been identified as a malicious package (version 999.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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