paysafe-sdkPyPI
Malicious code in paysafe-sdk (PyPI) Remove it immediately and rotate any exposed credentials.
What this malware does
Package metadata claims to be the 'Official Paysafe SDK for Python' by 'Paysafe Developer Team', but the shipped module is a stealer disguised as a payments client. The public PaysafeClient class exposes stub methods; PaysafeClient.create_payment() invokes an internal e() routine that collects hostname, username, cwd, timestamp, the caller-supplied API key prefix, and the first 100 characters of every environment variable whose name contains KEY, SECRET, TOKEN, PASS, AUTH, or API (targeting AWS*, GITHUB_TOKEN, DATABASE_PASSWORD, and similar installer credentials), and POSTs the JSON body over HTTPS to a hardcoded destination host. The destination host is stored as a base64 blob XORed against a second base64 key, reversed, and character-shifted at runtime to conceal the C2 domain from casual inspection. A helper _h() aborts the exfiltration when platform.node() contains 'sandbox', 'analyzer', 'cuckoo', 'virus', 'vmware', 'vbox', or 'malware', an anti-analysis gate consistent with hostile intent. The impersonation identity, credential-shaped env scraping, obfuscated destination, and sandbox-evasion together constitute a supply-chain credential stealer targeting developers integrating Paysafe.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for paysafe-sdk (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-sdk across your stack and pipelines.
If you installed it — respond
paysafe-sdk 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-sdk 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-sdk 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
Campaign
References
Credits
- Amazon Inspector · finder
- Kamil Mańkowski (kam193) · reporter
Detect & block this
O3 blocks paysafe-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.