Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Malicious code in @axon-web/icons (npm)

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm @axon-web/icons

    Affected
    >= 99.0.0, <= 99.0.0>= 2.0.0, <= 2.0.0
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

--- _-= Per source details. Do not edit below this line.=-_

Source: amazon-inspector (ee650ff91eeb70cc76f880c6b66b586b21c471c95eac22a9e23160aaffa45a58) The package is advertised as an SVG icon library but, on require, runs an IIFE that 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-style out-of-band interaction collector. The hostname and username of the installing machine are leaked to a non-first-party DNS endpoint over outbound DNS, bypassing HTTP egress controls. The same import-time code enumerates process.env keys matching /token|secret|key|pass|aws|github|npm/i and prints the matching names alongside hostname, user, cwd, and Node version. No icon-library functionality justifies DNS beaconing or credential-name enumeration, and the host identity is sent to a destination the caller did not configure.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from osv record MAL-2026-18433

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: mal-2026-18433

Advisory: Malicious code in @axon-web/icons (npm)
IDs: mal-2026-18433
Record: https://patchnext.com/advisories/mal-2026-18433 (revision 1, source checked 2 Nov 2026, 06:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @axon-web/icons: affected >= 99.0.0, <= 99.0.0; >= 2.0.0, <= 2.0.0

## Suggested inspection (read-only)
- `npm ls @axon-web/icons --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @axon-web/icons.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/MAL-2026-18433 (OSV record MAL-2026-18433 lists affected ranges: npm @axon-web/icons >=99.0.0 =2.0.0 <=2.0.0)

Commands are suggestions: review each one before running it.

Loading voting…