Malware in @403name/electron-buidler
The npm package @403name/electron-buidler contained malware that provided full system compromise to attackers. Any computer with this package installed should be considered fully compromised and all secrets and keys rotated from a different machine.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @403name/electron-buidler
The npm package @403name/electron-buidler was found to contain malware. According to the GitHub advisory, any computer that has 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 computer. While the malicious package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning there is no guarantee that removing the package alone will remove all malicious software resulting from the installation.\n\nThe package has been identified and removed from distribution, but users who installed it should treat their systems as fully compromised and take immediate remediation steps.
Indicators of compromise
- Packages
- @403name/electron-buidler
Remediation
- Immediately isolate any computer that had @403name/electron-buidler installed from the network
- From a different, uncompromised computer, rotate all secrets, keys, credentials, and tokens that may have been stored on the affected system
- Remove the @403name/electron-buidler package from the affected system
- Perform a full security audit and malware scan of the affected system
- Consider full system rebuild or replacement if the system handles sensitive operations
- Review access logs and audit trails for any unauthorized activity during the period the package was installed
Sources
- GitHub Advisory GHSA-h23r-x34f-p95m · GitHub Advisory Database
Cite this entry
"Malware in @403name/electron-buidler." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 27, 2026; last updated July 27, 2026. https://supplychainattack.org/incident/malware-in-403name-electron-buidler-qjqeck
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 test2221 (npm)
The npm package test2221 version 2.2.4 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
npmCompromised package - containedcritical
Malware in n8n-nodes-trust-me-im-totally-safe
Malware was discovered in the npm package n8n-nodes-trust-me-im-totally-safe, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
npmCompromised package - activecritical
Malware in litespeed-cache
Malware discovered in the npm package litespeed-cache. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.
npmCompromised package - containedcritical
Malware in open-worker-cli
Malware was discovered in the npm package open-worker-cli. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
npmCompromised package