Malware in @simplipayng/checkout
The npm package @simplipayng/checkout was found to contain malware. 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
- @simplipayng/checkout
The npm package @simplipayng/checkout was identified as containing malware by GitHub Security Advisory GHSA-cvhm-4vf7-gq9p. The advisory indicates that any computer with this package installed or running should be considered fully compromised.\n\nAccording to the advisory, all secrets and keys stored on affected computers should be rotated immediately from a different, uncompromised system. While the package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning removal of the package alone may not eliminate all malicious software resulting from the installation.\n\nThe incident was disclosed on 2026-08-06 via GitHub's advisory system.
Indicators of compromise
- Packages
- @simplipayng/checkout
Remediation
- Immediately rotate all secrets and keys stored on affected computers from a different, uncompromised system
- Remove the @simplipayng/checkout package from all systems
- Conduct a full security audit and malware scan of any system that had this package installed
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical systems are involved
Sources
- GitHub Advisory GHSA-cvhm-4vf7-gq9p · GitHub Advisory Database
Cite this entry
"Malware in @simplipayng/checkout." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 6, 2026; last updated August 6, 2026. https://supplychainattack.org/incident/malware-in-simplipayng-checkout-1mjc3z
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in fetch-runtime
Malware was discovered in the npm package fetch-runtime. Any system with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package - resolvedcritical
Malicious code in ghazaly (npm)
The npm package ghazaly version 99.9.0 contained malicious code that executed a postinstall hook to collect system information (hostname, current user, IP addresses) and exfiltrate it to a Burp Collaborator domain. The package exhibited dependency-confusion characteristics with a high version number and nonsense dependencies.
npmCompromised packageDependency confusion - containedcritical
Malicious code in base65-13x (npm)
base65-13x@5.0.2 on npm contains malicious obfuscated code disguised as a legitimate base-x library. The decode() function executes a ~123KB VM-style payload with dynamic code construction and network I/O capabilities.
npmCompromised package - containedcritical
Malicious code in kit-vim-map (npm)
The npm package kit-vim-map contained malicious code that executes a remote-controlled Linux ELF binary on installation, providing the attacker with arbitrary RCE, persistence, and file exfiltration capabilities. The binary beacons to C2 server 217.60.77.63 and establishes persistence via systemd user units.
npmCompromised packageMalicious commit