Which versions of @nimbusedge2/xa are malicious?

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

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

@nimbusedge2/xa 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/xa — how do I know if it already compromised me?

If @nimbusedge2/xa 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/xa part of a known attack campaign?

Yes — @nimbusedge2/xa is associated with the IN-MAL-2026-020196 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/xa 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/xa (version 1.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @nimbusedge2/xa across your stack and pipelines.

Malicious package

@nimbusedge2/xanpm

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

Malicious code in @nimbusedge2/xa (npm)

MAL-2026-16306

Immediate action

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

npm uninstall @nimbusedge2/xa

What this malware does

package.json declares a preinstall lifecycle script that runs an interactive bash reverse shell to the hardcoded host 147.93.157.202.nip.io on TCP port 8080 and pipes the shell's output through curl to http://canarytokens.com/terms/7dc94zmd3so67n5vbz5bxmt7v/contact.php. Because preinstall fires automatically on npm install, any machine that installs this package attempts to grant a remote party interactive command execution on the installer's host and unconditionally beacons install-time output over plain HTTP to a third-party tracking endpoint. The nip.io wrapper resolves the bare IP 147.93.157.202 without DNS registration, and the destination and token are hardcoded in the manifest with no caller configuration path.

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

537505221bc3cd73b0d5a60062d6ad127211b2d1be1f1cdfdac13053e2224a11

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/xa (version 1.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @nimbusedge2/xa across your stack and pipelines.
If you installed it — respond
@nimbusedge2/xa 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/xa 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/xa 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/xa on npm has been identified as a malicious package (version 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020196

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @nimbusedge2/xa-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