Malware in typeorm-encrypt
Malware discovered in the npm package typeorm-encrypt. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with typeorm-encrypt installed or running
- Ecosystems
- Attack vectors
- Affected entities
- typeorm-encryptnpm package
A critical malware incident has been identified in the npm package typeorm-encrypt, disclosed via GitHub Advisory GHSA-f7h6-4xj8-8qh7 on June 11, 2026.\n\nAny computer with typeorm-encrypt installed or running should be considered fully compromised. The malware grants outside entities full control of affected systems, potentially exposing all secrets and keys stored on those machines.\n\nImmediate action is required: all secrets and keys should be rotated from a different, unaffected computer. While the package should be removed, complete removal of all malicious software cannot be guaranteed due to the level of system compromise.\n\nThis is an active incident affecting the npm ecosystem.
Indicators of compromise
- Packages
- typeorm-encrypt
Remediation
- Immediately rotate all secrets and keys from a different, unaffected computer
- Remove the typeorm-encrypt package from all affected systems
- Conduct a full security audit of any system that had typeorm-encrypt installed
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if complete malware removal cannot be verified
- Notify all users and systems that may have been affected by this compromise
Sources
- GitHub Advisory GHSA-f7h6-4xj8-8qh7 · GitHub Advisory Database
Cite this entry
"Malware in typeorm-encrypt." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 11, 2026; last updated June 11, 2026. https://supplychainattack.org/incident/malware-in-typeorm-encrypt-ukgy7w
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- activecritical
Malware in chain-manager
Malware discovered in the npm package chain-manager. Systems with this package installed or running are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malicious code in @finxsecdemo/utils (npm)
The npm package @finxsecdemo/utils version 1.0.2 was identified as malicious by the OpenSSF Package Analysis project. The package communicates with a domain associated with malicious activity.
npmCompromised package - containedcritical
Malware in @bowozzz/baileys
The npm package @bowozzz/baileys contained malware that grants full system compromise to attackers. Any computer with this package installed should be considered fully compromised and all secrets and keys rotated immediately from a different machine.
npmCompromised package - containedcritical
Malicious code in blots (npm)
The npm package 'blots' version 2.1.0 was identified by the OpenSSF Package Analysis project as containing malicious code that executes commands associated with malicious behavior. The package has been flagged in the OpenSSF malicious packages database.
npmCompromised package