Malware in checkout-mobile-pay-button
The npm package checkout-mobile-pay-button contains malware that provides full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- checkout-mobile-pay-button
The npm package checkout-mobile-pay-button has been identified as containing 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 system. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise, as the attacker may have gained full control of the system.\n\nThis is a critical supply chain attack affecting the npm ecosystem, with potential impact to any developer or system that has installed or executed this package.
Indicators of compromise
- Packages
- checkout-mobile-pay-button
Remediation
- Immediately isolate any computer that has installed or run this package from the network
- Rotate all secrets, API keys, credentials, and signing keys from a different, uncompromised computer
- Remove the checkout-mobile-pay-button package from all systems
- Perform a full security audit and malware scan of affected systems
- Review all access logs and activity on affected systems for signs of unauthorized access or data exfiltration
- Consider the affected systems as potentially fully compromised and plan for complete rebuild if critical systems are involved
Sources
- GitHub Advisory GHSA-c2h8-p68f-vf8m · GitHub Advisory Database
Cite this entry
"Malware in checkout-mobile-pay-button." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 18, 2026; last updated August 18, 2026. https://supplychainattack.org/incident/malware-in-checkout-mobile-pay-button-ghkjrr
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 github-policy-bot (npm)
The npm package github-policy-bot contained malicious code that exfiltrated host identifiers and environment metadata during installation via a postinstall script. The package name shadowed a legitimate Google-owned repository and was authored under a placeholder account claiming security research purposes.
npmCompromised packageTyposquatting - containedcritical
Malicious code in crypto-javas (npm)
The npm package crypto-javas contains malicious code in its postinstall hook and main entrypoint that harvests environment variables (including CI secrets like AWS_*, GITHUB_TOKEN, NPM_TOKEN) and exfiltrates them to an attacker-controlled backend. The package is presented deceptively as @wizlabs/js-crypto with a placeholder repository.
npmCompromised packageTyposquatting - containedcritical
Malicious code in flydev (npm)
The npm package flydev contains malicious code designed to destroy Windows systems. The package masquerades as a utility but executes destructive operations including filesystem deletion, process termination, memory exhaustion, and fork bombs when invoked.
npmCompromised package - containedcritical
Malicious code in npm-wold (npm)
npm-wold@1.1.1 contains malicious code in its postinstall script that fetches remote JSON from a hardcoded endpoint and dynamically invokes attacker-controlled functions with attacker-supplied arguments, enabling code execution at install time.
npmCompromised package