Malware in async-lock-queue
Malware discovered in the npm package async-lock-queue. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with async-lock-queue installed or running
- Ecosystems
- Attack vectors
- Affected entities
- async-lock-queue
The npm package async-lock-queue has been identified as containing malware. According to the GitHub Advisory (GHSA-h6x7-5w93-p56j), 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. The package should be removed, though there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the compromise.\n\nThis represents a critical supply chain attack through a compromised package in the npm ecosystem.
Indicators of compromise
- Packages
- async-lock-queue
Remediation
- Immediately remove the async-lock-queue package from all systems
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Audit system logs for unauthorized access or activity
- Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical systems are involved
- Check for any other suspicious packages or modifications on affected systems
- Monitor for any lateral movement or persistence mechanisms that may have been installed
Sources
- GitHub Advisory GHSA-h6x7-5w93-p56j · GitHub Advisory Database
Cite this entry
"Malware in async-lock-queue." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 13, 2026; last updated August 13, 2026. https://supplychainattack.org/incident/malware-in-async-lock-queue-o7qk8h
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