Malware in zredis-typed
The npm package zredis-typed was found to contain malware. Systems with this package installed are considered fully compromised and require immediate remediation including secret rotation and package removal.
- Disclosed
- Last updated
- Blast radius
- Any system with zredis-typed installed
- Ecosystems
- Attack vectors
- Affected entities
- zredis-typednpm package containing malware
The npm package zredis-typed was identified as containing malware. GitHub Security Advisory GHSA-rmhj-j5m8-3cxj documents this incident.\n\nAny computer with this package installed or running should be considered fully compromised. The advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, unaffected system.\n\nWhile the package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning removal of the package alone may not eliminate all malicious software resulting from the installation.\n\nAffected package: zredis-typed (npm).
Indicators of compromise
- Packages
- zredis-typed
Remediation
- Immediately rotate all secrets and keys from a different, unaffected computer
- Remove the zredis-typed package from all affected systems
- Conduct a full security audit of any system that had zredis-typed installed
- Consider the affected system(s) as potentially fully compromised and take appropriate incident response measures
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
Sources
- GitHub Advisory GHSA-rmhj-j5m8-3cxj · GitHub Advisory Database
Cite this entry
"Malware in zredis-typed." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 7, 2026; last updated July 7, 2026. https://supplychainattack.org/incident/malware-in-zredis-typed-jxp8j4
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