Malicious code in paysafe-card-payments (npm)
MAL-2026-2551 · GHSA-9c83-p69j-8r99
Published · Modified
Dependency scanning
Check whether paysafe-card-payments is in your codebase
Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.
Description
__
Source: amazon-inspector (fd96859314d03d59ade846da5a5e56c7ae94d0590b341daba6a96438499c7bfa)
The package paysafe-card-payments was found to contain malicious code.
Source: ghsa-malware (cd85d2e170a5c21c263e66aa282d39dbef91765c1eed38b1ea964dcd9a48a906)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Source: ossf-package-analysis (3028f6f9f0152f37fcff20c7b8e1a1894193ac7b5a0e9474d4f996848cc78da8)
The OpenSSF Package Analysis project identified 'paysafe-card-payments' @ 99.99.2 (npm) as malicious.
It is considered malicious because:
- The package executes one or more commands associated with malicious behavior.
References
Ready to move
Start Securing
Free, no credit card | First findings in minutes