Malware in @lazyutil/dater
Malware discovered in the npm package @lazyutil/dater. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @lazyutil/dater
A critical malware incident has been identified in the npm package @lazyutil/dater. According to the GitHub Advisory (GHSA-gjrj-3f9w-gpmr), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated from a different, uncompromised system. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the package installation, given the potential for full system compromise.\n\nAffected users should treat this as a critical security incident requiring comprehensive system remediation beyond simple package removal.
Indicators of compromise
- Packages
- @lazyutil/dater
Remediation
- Immediately isolate affected systems from the network
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the @lazyutil/dater package
- Perform a comprehensive security audit and malware scan of affected systems
- Consider full system reimaging if the system handles sensitive data
- Review system logs for any unauthorized access or activity
- Monitor for any signs of persistence or lateral movement
Sources
- GitHub Advisory GHSA-gjrj-3f9w-gpmr · GitHub Advisory Database
Cite this entry
"Malware in @lazyutil/dater." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 13, 2026; last updated August 13, 2026. https://supplychainattack.org/incident/malware-in-lazyutil-dater-1jra5t
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