Malicious code in imgdecode (npm)
Published Sources: OSV (Schadpakete)
- Malicious package
What is affected, what to do
Uninstall the package, isolate affected environments and rotate credentials that were available during installation.
Not sure whether and how you are affected? Ask a question about this vulnerability
Malicious package
npmimgdecode
“imgdecode” is registered as malicious in the npm repository. Anyone who installed the package should uninstall it immediately, isolate affected environments and rotate credentials that were present during installation.
Affected versions (4)
- 1.0.0
- 1.0.1
- 1.0.2
- 1.0.3
purl: pkg:npm/imgdecode
Sources (7)
ghsa-malware
GHSA-hw69-vrvf-87h5Versions from this source: 1.0.1
sha256: 3c49d68e668c31b846588dba958146553f2f144a6778073dfeeffd14af78faf4
ghsa-malware
GHSA-hw69-vrvf-87h5Versions from this source: 1.0.0, 1.0.2, 1.0.1
sha256: 5c497e24555a674695aaa44d1bd306819aa5251efaeb124dbd1053677ddab94e
ghsa-malware
GHSA-hw69-vrvf-87h5Versions from this source: 1.0.0, 1.0.2, 1.0.1
sha256: 71220887f5fac059e03acb9fe206b6d19c3f8d2f4e99e99546069cdae171d3e0
amazon-inspector
IN-MAL-2026-021934Versions from this source: 1.0.0
sha256: 2c5eefceab716b4d4fb334a60f858918f37eb04c6806ddd980617d02bc10989d
amazon-inspector
IN-MAL-2026-021912Versions from this source: 1.0.2
sha256: 8d35e9f4292a2c57b47ea07b9202c69623374c4c6afaa588ff849d213ffbbef2
amazon-inspector
IN-MAL-2026-021941Versions from this source: 1.0.3
sha256: a7487eb7f1ae8aed3f20deb74664ded284b714e71206bc88b4445e283797c5ca
amazon-inspector
IN-MAL-2026-022257Versions from this source: 1.0.1
sha256: cec9a4f0d367a10af8441401091b0cd42fa52143f7bc10f438dff9793a0d69f0
The OSSF `malicious-packages` namespace lists packages flagged as malicious by static analysis or sandbox detonation. An entry here is a confirmed finding, not a suspicion.
Metrics
—
Priority
No value is available for this vulnerability.
—
CVSS v3
No value is available for this vulnerability.
—
EPSS score
No value is available for this vulnerability.
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 30.00 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
-= 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 in the host Node process immediately on module load, so any consumer that imports imgdecode on a win32-x64 host runs the packed binary, while all other platforms silently pull in and execute whatever code the imgbundle dependency contains. The combination of a facade JS stub, a README/API mismatch, a generic throwaway author identity, and a packed Windows PE delivered via require is a dependency-forwarder plus native-dropper shape rather than a working library.
Source: ghsa-malware (3c49d68e668c31b846588dba958146553f2f144a6778073dfeeffd14af78faf4)
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.