Which versions of stripe-client-py are malicious?

The following PyPI versions of stripe-client-py are flagged malicious: 1.0. Treat any of these as compromised.

How do I remediate stripe-client-py if I installed it?

Remove stripe-client-py 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.

I already installed stripe-client-py — how do I know if it already compromised me?

If stripe-client-py 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.

Is stripe-client-py part of a known attack campaign?

Yes — stripe-client-py is associated with the RLMA-2024-04848, RLUA-2024-09315 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 stripe-client-py across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for stripe-client-py (version 1.0).

Malicious package

stripe-client-pyPyPI

stripe-client-py is a confirmed malicious PyPI package (MAL-2024-6045) that executes malicious code on install (malicious version 1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in stripe-client-py (PyPI)

MAL-2024-6045

Immediate action

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

pip uninstall stripe-client-py

Malicious versions

1 flagged

1.0

Indicators of compromise (SHA-256)

c731f19040a5eca96f944922456516f300f4591ea3be8c6cf490c673618da695

8c098a49c405c72cac67f41bd8251905ebcaeeda739f9a32f4a539f81e4f1d76

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for stripe-client-py (version 1.0).
If you installed it — respond
Remove stripe-client-py 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.
Did it already run?
If stripe-client-py 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. stripe-client-py on PyPI has been identified as a malicious package (version 1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-04848RLUA-2024-09315

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks stripe-client-py-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database