@axon-web/iconsnpm
Advisory published Updated
@axon-web/icons is a confirmed malicious npm package (MAL-2026-18433) that steals credentials and exfiltrates sensitive data (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @axon-web/icons (npm)
What this malware does
On require, index.js constructs an identifier from os.hostname() and process.env.USER/USERNAME and issues a DNS resolve against a subdomain of nxsqlpejfpamagxctjyv4c9qj1gfdtzwi.oast.fun — an interactsh/OAST out-of-band collector — leaking the installer's hostname and OS username to an attacker-controlled DNS server as a side effect of module load. The same file enumerates process.env keys matching /token|secret|key|pass|aws|github|npm/i and writes the matching key names to stdout, which is reconnaissance of credential-bearing environment variables. The package presents as an icons library at version 99.0.0 with no icon content, consistent with a dependency-confusion or typosquat payload rather than a legitimate library.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for @axon-web/icons (version 99.0.0).
If you installed it — respond
@axon-web/icons 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 @axon-web/icons 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @axon-web/icons-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.