Malware in @doaction/pay
Malware was discovered in the npm package @doaction/pay. Systems with this package installed or running should be considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @doaction/pay
A critical malware incident was identified in the npm package @doaction/pay, published as GitHub Advisory GHSA-55rv-c39c-944m on June 9, 2026.\n\nAny computer with this package installed or running is considered fully compromised. The malware may have granted outside entities full control of affected systems.\n\nImmediate remediation requires rotating all secrets and keys from a different, uncompromised computer. While the package should be removed, complete removal of all malicious software cannot be guaranteed due to the potential for full system compromise.\n\nUsers should assume that removing the package alone may not fully remediate the compromise.
Indicators of compromise
- Packages
- @doaction/pay
Remediation
- Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
- Remove the @doaction/pay package from all affected systems
- Conduct a full security audit of any system that had this package installed
- Monitor affected systems for signs of persistent compromise or backdoors
- Review and revoke any API keys, tokens, or credentials that may have been exposed
- Consider full system reimaging if the package was installed on production or sensitive systems
Sources
- GitHub Advisory GHSA-55rv-c39c-944m · GitHub Advisory Database
Cite this entry
"Malware in @doaction/pay." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 9, 2026; last updated June 9, 2026. https://supplychainattack.org/incident/malware-in-doaction-pay-h76xyd
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 sme-rko-finance-front-operations-feed-models (npm)
The npm package sme-rko-finance-front-operations-feed-models contained malicious code that downloads and executes attacker-controlled native binaries from remote servers upon package load. The malware uses obfuscation techniques including fragmented string arrays, platform-specific endpoints, and DNS TXT record fallbacks to evade detection.
npmCompromised package - resolvedcritical
Malicious code in modern-localization (npm)
The npm package modern-localization contained malicious code that fetches and executes arbitrary JavaScript from a remote jsonbin.io endpoint on server-side require, with no integrity verification. The payload is executed with full Node.js privileges via Function() or child_process.fork().
npmCompromised package - resolvedcritical
Malicious code in sme-rko-finance-front-operations-tax (npm)
The npm package sme-rko-finance-front-operations-tax contained malicious code that downloads and executes platform-specific binaries from attacker-controlled infrastructure on require. The package was identified and reported by OpenSSF's malicious-packages project.
npmCompromised package - resolvedcritical
Malicious code in localization-fixer (npm)
The npm package localization-fixer contained malicious code that fetches and executes arbitrary JavaScript from attacker-controlled jsonbin.io endpoints on package require, granting full Node.js capabilities to remote payloads.
npmCompromised package