Which versions of paysafe-payments are malicious?

The following PyPI versions of paysafe-payments are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate paysafe-payments if I installed it?

paysafe-payments is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed paysafe-payments — how do I know if it already compromised me?

If paysafe-payments was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is paysafe-payments part of a known attack campaign?

Yes — paysafe-payments is associated with the 2026-07-paysafe-api, IN-MAL-2026-008602 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find paysafe-payments across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for paysafe-payments (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging paysafe-payments across your stack and pipelines.

Malicious package

paysafe-paymentsPyPI

Malicious code in paysafe-payments (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-6928

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

pip uninstall paysafe-payments

What this malware does

Package impersonates the Paysafe payments SDK (metadata claims 'Paysafe Developer Team', 'Paysafe Payments processing library') but its advertised PaysafeClient.create_payment() method never contacts api.paysafe.com. Instead, on every invocation it collects all environment variables whose names contain KEY, SECRET, TOKEN, PASS, AUTH, or API (truncated to 100 characters each), plus the host's node name, current user, working directory, and the first 10 characters of the caller-supplied Paysafe API key, and POSTs them as JSON to a hardcoded remote host. The destination hostname is hidden as two base64 blobs (_k, _cb) that are XOR-combined with a rotating key, reversed, and character-shifted by -11 to reconstruct the C2 endpoint at runtime. A hostname check against 'sandbox', 'analyzer', 'cuckoo', 'virus', 'vmware', 'vbox', and 'malware' suppresses the beacon on analysis systems. After exfiltration the function returns a stubbed {'status':'success'} response so callers believe the payment succeeded. The combination of brand impersonation, stubbed non-functional API, multi-layer C2 obfuscation, sandbox evasion, and bulk credential-shape environment scraping is unambiguously malicious.

When using a provided class, the code exfiltrates basic data and parts of sensitive env variables to a remote host.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-07-paysafe-api

Reasons (based on the campaign):

exfiltration-env-variables
dependency-confusion
action-hidden-in-lib-usage
The package contains code to detect if it is running in a sandbox environment.
obfuscation

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

cc8e13806589e7fbb3dbe284624b88d6de8c030f32c04c20f8c76af059f33515

f36b53b707131144693edb59b95fe127d3b0dbbcd621691792247e3e9a33428c

7e2b7f287703755dab866acf1047a148e321d06a84353238936eaba58b6e7fda

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for paysafe-payments (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging paysafe-payments across your stack and pipelines.
If you installed it — respond
paysafe-payments is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If paysafe-payments was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks paysafe-payments before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. paysafe-payments on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-07-paysafe-apiIN-MAL-2026-008602

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

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

Malware detection Runtime egress monitoring