Which versions of @nimbusedge2/authxsas1 are malicious?

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

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

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

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

Yes — @nimbusedge2/authxsas1 is associated with the IN-MAL-2026-020200 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/authxsas1 across my projects, lockfiles, and CI pipelines?

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

Malicious package

@nimbusedge2/authxsas1npm

Advisory published Sep 21, 2026Updated Sep 21, 2026

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

MAL-2026-16304

Immediate action

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

npm uninstall @nimbusedge2/authxsas1

What this malware does

package.json declares a preinstall lifecycle script that runs automatically on npm install. The script uses curl to fetch the cloud instance metadata service (169.254.169.254, accessed via the nip.io wildcard-DNS wrapper 169.254.169.254.nip.io/latest/meta-data/), base64-encodes the response, and POSTs it to a hardcoded third-party endpoint at http://canarytokens.com/terms/7dc94zmd3so67n5vbz5bxmt7v/contact.php. On cloud and CI installers this discloses instance identity metadata and, where IMDSv1 is reachable, temporary IAM credentials to the destination. The package's description field self-labels the beacon as an 'Authorized report' with a wearehackerone.com contact address; that label is author-controlled and does not change the behavior class — installing the package causes installer-side host and cloud metadata to be sent off-host to a canarytoken beacon.

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

0b27280b8f4c1e044e49b77e58c7c8de895a002f51be51756bc40e909d3f6fa1

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @nimbusedge2/authxsas1 (version 1.1.0).
If you installed it — respond
@nimbusedge2/authxsas1 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/authxsas1 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/authxsas1 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-020200

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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