Malware in lessload
Malware was discovered in the npm package lessload, resulting in full system compromise for any installation. The package should be removed immediately and all secrets and keys rotated from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with lessload installed or running
- Ecosystems
- Attack vectors
- Affected entities
- lessload
A critical malware incident was identified in the npm package lessload. According to the GitHub Security Advisory, any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate removal of the package and rotation of all secrets and keys from a different, unaffected computer. However, due to the severity of the compromise, there is no guarantee that removing the package alone will eliminate all malicious software that may have been installed as a result of the initial infection.\n\nThis represents a complete system compromise vector and requires comprehensive remediation beyond simple package removal.
Indicators of compromise
- Packages
- lessload
Remediation
- Immediately remove the lessload package from all affected systems
- Rotate all secrets, API keys, credentials, and authentication tokens from a clean, unaffected computer
- Perform a comprehensive security audit and malware scan of any system that had lessload installed
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if the compromise cannot be fully verified as contained
- Monitor for any suspicious activity on accounts and systems that may have been affected
Sources
- GitHub Advisory GHSA-62jh-gmff-xfrm · GitHub Advisory Database
Cite this entry
"Malware in lessload." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 20, 2026; last updated August 20, 2026. https://supplychainattack.org/incident/malware-in-lessload-8c6fz8
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 rust-testing-utils (npm)
The npm package rust-testing-utils contained malicious code that impersonates the pino logger and executes remotely-fetched code with arbitrary privileges. The package spawns a child process that decodes a hardcoded URL, fetches attacker-controlled content, and executes it via Function constructor with full module-loading capability.
npmCompromised packageMalicious commit - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malware in hydration-dim-kit
Malware was discovered in the npm package hydration-dim-kit. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package