Which versions of @3stripes/auth are malicious?

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

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

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

If @3stripes/auth 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/auth across my projects, lockfiles, and CI pipelines?

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

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

Malicious package

@3stripes/authnpm

Advisory published Mar 15, 2026Updated Mar 23, 2026

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

MAL-2026-1425

Immediate action

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

npm uninstall @3stripes/auth

What this malware does

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

The OpenSSF Package Analysis project identified '@3stripes/auth' @ 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)

6dfef2aa5b1531e49858972a00975d216023431edb51a77bfb48daff095f6b58

152509a4bd82adf6364c22476faa63746b5ddc6649dd64a7fdf96ff5e67ebc13

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @3stripes/auth (version 999.0.2).
If you installed it — respond
Remove @3stripes/auth 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/auth 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/auth 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/auth-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