Malware in filifecycleserv-paypal
Malware discovered in the npm package filifecycleserv-paypal. Systems with this package installed or running should be considered fully compromised. All secrets and keys must 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
- filifecycleserv-paypal
A malicious npm package named filifecycleserv-paypal has been identified and published to the npm registry. The package contains malware that grants full control of affected systems to an outside entity.\n\nAny computer that has this package installed or running should be considered fully compromised. All secrets, keys, and credentials stored on affected systems should be rotated immediately from a different, unaffected computer.\n\nWhile the package should be removed, removal alone may not eliminate all malicious software that resulted from the installation, as the attacker may have gained full system control. A comprehensive security review and potential system rebuild is recommended.
Indicators of compromise
- Packages
- filifecycleserv-paypal
Remediation
- Remove the filifecycleserv-paypal package immediately from all systems
- Rotate all secrets, keys, and credentials from a different, unaffected computer
- Conduct a comprehensive security audit of affected systems
- Consider full system rebuild or forensic analysis to ensure complete removal of malicious software
- Review npm package dependencies to identify if filifecycleserv-paypal was a transitive dependency
- Monitor affected systems for signs of compromise or unauthorized access
Sources
- GitHub Advisory GHSA-gj5f-c6h7-9v2f · GitHub Advisory Database
Cite this entry
"Malware in filifecycleserv-paypal." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 27, 2026; last updated July 27, 2026. https://supplychainattack.org/incident/malware-in-filifecycleserv-paypal-gjpqne
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