Malicious code in imgdecode (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 imgdecode
- Affected
- every version
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record MAL-2026-18196 lists affected ranges: npm imgdecode >=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 (8d35e9f4292a2c57b47ea07b9202c69623374c4c6afaa588ff849d213ffbbef2) imgdecode@1.0.2 presents itself as a native image buffer decoder but ships a 224-byte index.js whose only runtime effect on require is to load the sibling package 'imgbundle' and attempt to require./prebuilds/win32-x64/imgdecode.node, swallowing errors. The exported API is a single load() that returns null, which does not correspond to the README's advertised exec(cmd, args) interface. The bundled prebuilds/win32-x64/imgdecode.node is a 703 KB Windows PE containing a non-standard.fptable3 section and obfuscated Windows API name fragments (e.g. 'EXClos', 'E\eHan', 'EPSlee' consistent with Close/Handle/Sleep under API-name hashing or XOR-stub packing) and no normal Node-API registration symbols — characteristics of packed/obfuscated native code, not a legitimate image-decoder addon. A.node file loaded via require executes native code…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from osv record MAL-2026-18196
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-hw69-vrvf-87h5 Advisory: Malicious code in imgdecode (npm) IDs: GHSA-hw69-vrvf-87h5 Record: https://patchnext.com/advisories/mal-2026-18196 (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 imgdecode: affected every version ## Suggested inspection (read-only) - `npm ls imgdecode --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 imgdecode. - 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-18196 (OSV record MAL-2026-18196 lists affected ranges: npm imgdecode >=0) Commands are suggestions: review each one before running it.
Loading voting…