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

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

Search your lockfiles and build artifacts for @nimbusedge2/xa (version 1.1.0).

Malicious package

@nimbusedge2/xanpm

Advisory published Sep 21, 2026Updated Sep 21, 2026

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

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for @nimbusedge2/xa (version 1.1.0).
If you installed it — respond
@nimbusedge2/xa 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/xa 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/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 C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database