Malware in gpaas-paypal
The npm package gpaas-paypal 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.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- gpaas-paypalnpm package containing malware
The npm package gpaas-paypal was identified as containing malware. According to the GitHub Advisory (GHSA-c77x-6gm9-q7mf), 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, 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\nThis represents a critical supply chain attack through a compromised npm package with potential for widespread impact across all systems where it was installed.
Indicators of compromise
- Packages
- gpaas-paypal
Remediation
- Immediately rotate all secrets and keys from a different, uncompromised computer
- Remove the gpaas-paypal package from all affected systems
- Conduct a full security audit of any system that had the package installed
- Monitor affected systems for signs of unauthorized access or persistence mechanisms
- Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical infrastructure
Sources
- GitHub Advisory GHSA-c77x-6gm9-q7mf · GitHub Advisory Database
Cite this entry
"Malware in gpaas-paypal." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 27, 2026; last updated July 27, 2026. https://supplychainattack.org/incident/malware-in-gpaas-paypal-15igmn
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