Malware in evm-typechain
Malware was discovered in the npm package evm-typechain. Systems with this package installed or running are considered fully compromised and require immediate remediation including secret rotation and package removal.
- Disclosed
- Last updated
- Blast radius
- Any system with evm-typechain installed or running
- Ecosystems
- Attack vectors
- Affected entities
- evm-typechainnpm package
A malware incident was identified in the npm package evm-typechain, published as GitHub Advisory GHSA-c4gm-jp6q-h9hq on 2026-07-07.\n\nAccording to the advisory, any computer with this package installed or running should be considered fully compromised. The malware grants outside entities full control of affected systems.\n\nImmediate remediation requires rotating all secrets and keys from a different, uncompromised computer. While the package should be removed, complete removal of all malicious software cannot be guaranteed due to the level of system compromise achieved.\n\nAffected users should treat their systems as potentially containing persistent malware beyond the package itself.
Indicators of compromise
- Packages
- evm-typechain
Remediation
- Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
- Remove the evm-typechain package from all affected systems
- Perform a full security audit and malware scan of any system that had evm-typechain installed
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if the system contained sensitive data or had privileged access
- Notify any services or systems that may have been accessed using credentials stored on compromised machines
Sources
- GitHub Advisory GHSA-c4gm-jp6q-h9hq · GitHub Advisory Database
Cite this entry
"Malware in evm-typechain." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 7, 2026; last updated July 7, 2026. https://supplychainattack.org/incident/malware-in-evm-typechain-17etjx
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in github-policy-bot (npm)
The npm package github-policy-bot contained malicious code that exfiltrated host identifiers and environment metadata during installation via a postinstall script. The package name shadowed a legitimate Google-owned repository and was authored under a placeholder account claiming security research purposes.
npmCompromised packageTyposquatting - containedcritical
Malicious code in crypto-javas (npm)
The npm package crypto-javas contains malicious code in its postinstall hook and main entrypoint that harvests environment variables (including CI secrets like AWS_*, GITHUB_TOKEN, NPM_TOKEN) and exfiltrates them to an attacker-controlled backend. The package is presented deceptively as @wizlabs/js-crypto with a placeholder repository.
npmCompromised packageTyposquatting - containedcritical
Malicious code in flydev (npm)
The npm package flydev contains malicious code designed to destroy Windows systems. The package masquerades as a utility but executes destructive operations including filesystem deletion, process termination, memory exhaustion, and fork bombs when invoked.
npmCompromised package - containedcritical
Malicious code in npm-wold (npm)
npm-wold@1.1.1 contains malicious code in its postinstall script that fetches remote JSON from a hardcoded endpoint and dynamically invokes attacker-controlled functions with attacker-supplied arguments, enabling code execution at install time.
npmCompromised package