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
- resolvedcritical
Malicious code in @dreamguyxeon/baileyx (npm)
@dreamguyxeon/baileyx, a Baileys WhatsApp Web API fork on npm, contains malicious code that silently auto-follows newsletters from a remote-controlled list after session setup. The package also patches the libsignal dependency to use a compromised version from @dgxeon13/libsignal-node.
npmCompromised packageMalicious commit - resolvedcritical
Malicious code in @dreamguyxeon/libsignal-node (npm)
@dreamguyxeon/libsignal-node is a malicious npm package that patches @whiskeysockets/baileys at import time to inject remote-controlled WhatsApp newsletter auto-follow code. The package was distributed as a dependency alias in my-auto-follow@1.0.3 and is part of a related malicious campaign.
npmCompromised packageMalicious commit - activecritical
Malicious code in my-auto-follow (npm)
The npm package my-auto-follow contains malicious code that silently auto-follows WhatsApp newsletters from an attacker-controlled list without user consent. The package also depends on a separate malicious libsignal patcher. This is part of an ongoing DGXeon campaign with related malicious packages already documented.
DgxeonnpmCompromised packageMalicious commit - containedcritical
Malware in nolimit-agent
Malware was discovered in the nolimit-agent npm package. Systems with this package installed are considered fully compromised and require immediate remediation including secret rotation and package removal.
npmCompromised package