NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

paysafe-card-paymentsnpm

Advisory published Updated

paysafe-card-payments is a confirmed malicious npm package (MAL-2026-2551) that executes malicious code on install (malicious versions 99.0.0, 99.99.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in paysafe-card-payments (npm)

MAL-2026-2551
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall paysafe-card-payments

What this malware does

The package paysafe-card-payments was found to contain malicious code.

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.

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.

Malicious versions

2 flagged
99.0.099.99.2

Indicators of compromise (SHA-256)

1df2649a893af24a22a6777831fc8f8fdbc2d576a74a6aa8a1ae327e9ce8ac6d
cd85d2e170a5c21c263e66aa282d39dbef91765c1eed38b1ea964dcd9a48a906
3028f6f9f0152f37fcff20c7b8e1a1894193ac7b5a0e9474d4f996848cc78da8
fd96859314d03d59ade846da5a5e56c7ae94d0590b341daba6a96438499c7bfa

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for paysafe-card-payments (2 malicious versions).

  2. If you installed it — respond

    Remove paysafe-card-payments from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If paysafe-card-payments was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. paysafe-card-payments on npm has been identified as a malicious package (versions 99.0.0, 99.99.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9c83-p69j-8r99

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks paysafe-card-payments-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

paysafe-card-payments (npm) malicious package — MAL-2026-2551 | O3 Security