Which versions of axelarjs-sdk are malicious?

The following npm versions of axelarjs-sdk are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate axelarjs-sdk if I installed it?

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

If axelarjs-sdk 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 axelarjs-sdk part of a known attack campaign?

Yes — axelarjs-sdk is associated with the GHSA-8cf8-9j3v-99g4 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 axelarjs-sdk across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for axelarjs-sdk (version 1.0.1).

Malicious package

axelarjs-sdknpm

Advisory published Nov 1, 2026Updated Nov 2, 2026

axelarjs-sdk is a confirmed malicious npm package (MAL-2026-18456) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in axelarjs-sdk (npm)

MAL-2026-18456

Immediate action

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

npm uninstall axelarjs-sdk

What this malware does

[email protected] takes the unscoped name of @axelar-network/axelarjs-sdk and has no functional code. Its preinstall script runs node preinstall.js on npm install, which POSTs the machine's hostname, the OS username and the local time to the Discord webhook https://canary.discord.com/api/webhooks/1566232728179843243/pM5rDIrCRrEpQRbA7ibaiQk1XOQlIftmBacA5s8jD8NvXn5W-rS832DOWHQS-G-j3N6U as "PC Notifier". It was published by the npm account cutekitten05, which published wallet-adapter-base, cutekitten-test, bigbob22-test and sol-wallet-adapter with the same script on 2026-11-01.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

e6d73764aa55df0753800957d7854d7821634c6556aa46f618b8e868b9bfd861

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for axelarjs-sdk (version 1.0.1).
If you installed it — respond
axelarjs-sdk 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 axelarjs-sdk 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. axelarjs-sdk on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-8cf8-9j3v-99g4

References

Credits

InvisiRisk, Inc. · finder

Detect & block this

O3 blocks axelarjs-sdk-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