Malware in type-plint
Malware was discovered in the npm package type-plint, resulting in full system compromise for any computer with the package installed or running. The advisory recommends immediate removal and rotation of all secrets and keys from a clean system.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- type-plint
A malicious package named type-plint was published to npm and contains malware that compromises any system where it is installed or executed. According to the GitHub Security Advisory GHSA-8mhh-r4mc-2293, any computer running this package should be considered fully compromised.\n\nThe advisory recommends that all secrets, keys, and credentials stored on affected systems be rotated immediately from a different, uncompromised computer. While the package should be removed, the advisory notes that full control of the system may have been granted to an external entity, meaning removal of the package alone may not eliminate all malicious software that was installed as a result.\n\nThis is a critical supply chain incident affecting the npm ecosystem, with potential impact to any developer or system that installed or ran this package.
Indicators of compromise
- Packages
- type-plint
Remediation
- Remove the type-plint package immediately from all systems
- Rotate all secrets, keys, and credentials from a clean, uncompromised computer
- Audit system logs for unauthorized access or activity during the period the package was installed
- Consider full system reimaging if the package was installed on production or sensitive systems
- Check for any other suspicious packages or modifications that may have been introduced
Sources
- GitHub Advisory GHSA-8mhh-r4mc-2293 · GitHub Advisory Database
Cite this entry
"Malware in type-plint." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 10, 2026; last updated July 10, 2026. https://supplychainattack.org/incident/malware-in-type-plint-wl519a
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 sme-rko-finance-front-operations-feed-models (npm)
The npm package sme-rko-finance-front-operations-feed-models contained malicious code that downloads and executes attacker-controlled native binaries from remote servers upon package load. The malware uses obfuscation techniques including fragmented string arrays, platform-specific endpoints, and DNS TXT record fallbacks to evade detection.
npmCompromised package - resolvedcritical
Malicious code in modern-localization (npm)
The npm package modern-localization contained malicious code that fetches and executes arbitrary JavaScript from a remote jsonbin.io endpoint on server-side require, with no integrity verification. The payload is executed with full Node.js privileges via Function() or child_process.fork().
npmCompromised package - resolvedcritical
Malicious code in sme-rko-finance-front-operations-tax (npm)
The npm package sme-rko-finance-front-operations-tax contained malicious code that downloads and executes platform-specific binaries from attacker-controlled infrastructure on require. The package was identified and reported by OpenSSF's malicious-packages project.
npmCompromised package - resolvedcritical
Malicious code in localization-fixer (npm)
The npm package localization-fixer contained malicious code that fetches and executes arbitrary JavaScript from attacker-controlled jsonbin.io endpoints on package require, granting full Node.js capabilities to remote payloads.
npmCompromised package