Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

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.

ShareXLinkedInHacker News
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

  1. 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.

  1. activecritical

    Malware in @doaction/auth

    Malware discovered in the npm package @doaction/auth. Systems with this package installed are considered fully compromised and require immediate remediation.

    npmCompromised package
  2. containedcritical

    Malware in @doaction/shared

    Malware was discovered in the npm package @doaction/shared. Systems with this package installed are considered fully compromised and require immediate remediation.

    npmCompromised package
  3. containedcritical

    Malware in transacts

    The npm package transacts was found to contain malware, resulting in full system compromise of any computer with the package installed or running. All secrets and keys should be rotated immediately from a different computer, and the package should be removed.

    npmCompromised package
  4. containedcritical

    Malware in buffer-utilities

    Malware was discovered in the npm package buffer-utilities, resulting in full system compromise for any installation. The package should be removed immediately and all secrets and keys rotated from a clean system.

    npmCompromised package