Which versions of @nimbusedge2/authxsas are malicious?

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

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

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

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

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

Malicious package

@nimbusedge2/authxsasnpm

@nimbusedge2/authxsas is a confirmed malicious npm package (MAL-2026-16303) 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/authxsas (npm)

MAL-2026-16303

Immediate action

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

npm uninstall @nimbusedge2/authxsas

What this malware does

The package's package.json declares a preinstall script that fires unconditionally on npm install. The script uses curl to query the cloud instance metadata service via the nip.io wildcard-DNS resolver (169.254.169.254.nip.io/latest/meta-data/), base64-encodes the response, and POSTs it over plain HTTP to a hardcoded canarytokens.com endpoint (http://canarytokens.com/terms/7dc94zmd3so67n5vbz5bxmt7v/contact.php). On installers running on AWS/GCP/Azure hosts with IMDS reachable, this leaks IAM role identifiers and, on IMDSv1, temporary cloud credentials to a third-party canary endpoint at install time. The tarball ships no source files; the manifest and its preinstall hook are the entire payload. The scope name and package name are consistent with a dependency-confusion / SSRF canary probe targeting an internal namespace.

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

0146259024cc8ef3a174ff98571fe4af975b3eecf9184a0a5339d42808243d10

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/authxsas (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/authxsas across your stack and pipelines.
If you installed it — respond
@nimbusedge2/authxsas 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/authxsas 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/authxsas 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/authxsas 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-020202

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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