Malware in datetime-toolkit
Malware was discovered in the npm package datetime-toolkit. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- datetime-toolkit
The npm package datetime-toolkit was found to contain malware. According to the GitHub Security Advisory (GHSA-hjx5-46c8-fm8p), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. While 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 that resulted from the installation.\n\nUsers should treat any system that has run this package as potentially containing persistent malware and take appropriate containment and recovery measures.
Indicators of compromise
- Packages
- datetime-toolkit
Remediation
- Remove the datetime-toolkit package immediately from all systems
- Rotate all secrets, API keys, and credentials from a clean, uncompromised computer
- Assume full system compromise and perform forensic analysis or complete system rebuild
- Audit all systems for signs of unauthorized access or persistence mechanisms
- Monitor for any suspicious activity on systems that previously had the package installed
Sources
- GitHub Advisory GHSA-hjx5-46c8-fm8p · GitHub Advisory Database
Cite this entry
"Malware in datetime-toolkit." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 19, 2026; last updated August 19, 2026. https://supplychainattack.org/incident/malware-in-datetime-toolkit-r6dytq
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in testingsmthb1g (npm)
The npm package testingsmthb1g contains malicious code in its postinstall script that acts as an install-time dropper, downloading and executing a Windows binary payload and exfiltrating platform information. The attack includes sandbox escape capabilities for WSL/virtualized Linux environments.
npmCompromised package - resolvedcritical
Malicious code in mutex-core (npm)
The npm package mutex-core, published under a name resembling the popular async-mutex library, contained malicious code including a staged loader that decrypts and executes hidden payloads. The package included obfuscated code that conditionally triggers AES-256-GCM decryption and execution of encrypted binary content when specific conditions are met.
npmCompromised package - containedcritical
Malicious code in tyepescript-cli (npm)
tyepescript-cli, a typosquat of the legitimate typescript package on npm, contains malicious postinstall code that downloads and executes a Windows binary (main.exe) and beacons to an attacker-controlled server. The package uses XOR obfuscation to hide URLs, commands, and IP addresses, with special logic to target both Windows and WSL environments.
npmTyposquattingCompromised package - containedcritical
Malicious code in commandor-cli (npm)
commandor-cli@1.0.0 on npm contains malicious postinstall script that downloads and executes a binary from an attacker-controlled GitHub repository. The script also beacons installation metadata to a command-and-control server and includes a PowerShell bridge to extend execution to Windows hosts on WSL systems.
npmCompromised packageMalicious commit