Malware in @petitcode/eb-retry
Malware discovered in the npm package @petitcode/eb-retry. The package is reported to provide full system compromise to attackers. All affected systems should be considered fully compromised.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @petitcode/eb-retry
A malicious npm package, @petitcode/eb-retry, has been identified as containing malware. According to the GitHub Advisory (GHSA-vfmg-ghq7-3rv3), 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 package installation.\n\nGiven the severity of the compromise, affected users should assume complete loss of system integrity and take appropriate incident response measures.
Indicators of compromise
- Packages
- @petitcode/eb-retry
Remediation
- Immediately remove the @petitcode/eb-retry package from all affected systems
- Rotate all secrets, API keys, credentials, and authentication tokens from a different, uncompromised computer
- Assume full system compromise and conduct a thorough security audit of affected systems
- Monitor affected systems for signs of persistent malware or unauthorized access
- Consider rebuilding affected systems from clean media if possible
- Review system logs and network traffic for indicators of compromise or data exfiltration
Sources
- GitHub Advisory GHSA-vfmg-ghq7-3rv3 · GitHub Advisory Database
Cite this entry
"Malware in @petitcode/eb-retry." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 13, 2026; last updated August 13, 2026. https://supplychainattack.org/incident/malware-in-petitcode-eb-retry-xfd5eu
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