Malware in @tinyfox/shapecheck
Malware was discovered in the npm package @tinyfox/shapecheck. Systems with this package installed or running are considered fully compromised, with potential for complete system takeover.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @tinyfox/shapecheck
A malware-laden version of the npm package @tinyfox/shapecheck was published and made available to users. The package is flagged as critical severity by GitHub's advisory system.\n\nAccording to the advisory, any computer that has installed or run this package should be considered fully compromised. The malware grants outside entities potential full control of affected systems.\n\nImmediate remediation requires rotating all secrets and keys from a separate, uncompromised computer, and removing the package. However, due to the level of system compromise, removal of the package alone may not eliminate all malicious software that was installed as a result.\n\nThe advisory was published on 2026-08-13 via GitHub's security advisory system.
Indicators of compromise
- Packages
- @tinyfox/shapecheck
Remediation
- Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
- Remove the @tinyfox/shapecheck package from all affected systems
- Perform a full security audit and malware scan of any system that had this package installed
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider the affected system(s) potentially compromised and plan for full rebuild if critical infrastructure
Sources
- GitHub Advisory GHSA-9q9p-jf58-9fxg · GitHub Advisory Database
Cite this entry
"Malware in @tinyfox/shapecheck." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 13, 2026; last updated August 13, 2026. https://supplychainattack.org/incident/malware-in-tinyfox-shapecheck-7hsb2r
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 pump-segments-sdk (npm)
The npm package pump-segments-sdk contained malicious code in a postinstall hook that exfiltrated sensitive system and npm configuration data to an attacker-controlled server. The package collected hostname, environment variables, system information, npm auth tokens, and attempted to read password hashes.
npmCompromised package - containedcritical
Malicious code in ts-rand-sdk (npm)
The npm package ts-rand-sdk contained malicious code disguised as a product catalog loader. When the advertised getTransactions() API was called, hidden obfuscated JavaScript was decoded and executed with full Node.js capabilities, enabling arbitrary filesystem, process, and network access on affected systems.
npmCompromised package - resolvedcritical
Malicious code in lodsh-cli (npm)
lodsh-cli, a typosquat of lodash-cli on npm, contained malicious code in its postinstall script that executed arbitrary remote code and exfiltrated system information. The package downloaded a Windows executable and sent platform data to a hardcoded IP address.
npmTyposquattingCompromised package - containedcritical
Malicious code in lodahsjs (npm)
The npm package lodahsjs is a typosquatting attack on 'lodash' that contains malicious code in its postinstall script. Upon installation, it exfiltrates system information to a C2 server and downloads and executes a Windows binary, with capability to bridge WSL environments to compromise the host Windows system.
npmCompromised packageTyposquatting