Malicious code in mx3dxhgic8xhd6 (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.
Affected packages
npm mx3dxhgic8xhd6
- Affected
- every version
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record MAL-2026-17936 lists affected ranges: npm mx3dxhgic8xhd6 >=0
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
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 (6c4fbf379ad5f6f1c43cb74ef7fbc66e56fe9b0c0edeaffd1f51bb9e5558c2bb) Package mx3dxhgic8xhd6@1.0.1 is published under a random-looking short name with only two files, one of which is an index.html containing a large obfuscator.io-style JavaScript payload. The script uses hex-named identifiers (_0x...), a ~500-entry shuffled string array returned by a decoder function, a rotating-array decoder loop, and runtime atob / String.fromCharCode calls, so no destination URLs, API endpoints, or data sinks are visible as plain text. The code's actual runtime behavior (network destinations, DOM injection, redirect/clipboard/credential sinks) cannot be determined without executing or de-obfuscating the payload. The shape — nonsense package name, HTML-as-payload, heavy string/control-flow obfuscation hiding all destinations — is consistent with phishing/ClickFix-style delivery pages rather than a conventional npm…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from osv record MAL-2026-17936
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-cqch-q2w2-r565 Advisory: Malicious code in mx3dxhgic8xhd6 (npm) IDs: GHSA-cqch-q2w2-r565 Record: https://patchnext.com/advisories/mal-2026-17936 (revision 1, source checked 30 Oct 2026, 06:05 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 mx3dxhgic8xhd6: affected every version ## Suggested inspection (read-only) - `npm ls mx3dxhgic8xhd6 --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 mx3dxhgic8xhd6. - 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-17936 (OSV record MAL-2026-17936 lists affected ranges: npm mx3dxhgic8xhd6 >=0) Commands are suggestions: review each one before running it.
Loading voting…