Which versions of stripe-backup are malicious?

The following RubyGems versions of stripe-backup are flagged malicious: 0.0.0. Treat any of these as compromised.

How do I remediate stripe-backup if I installed it?

Remove stripe-backup 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-backup — how do I know if it already compromised me?

If stripe-backup 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-backup part of a known attack campaign?

Yes — stripe-backup is associated with the RLMA-2025-06631, RLUA-2026-09466 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-backup across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for stripe-backup (version 0.0.0).

Malicious package

stripe-backupRubyGems

Advisory published Dec 23, 2025Updated Sep 24, 2026

stripe-backup is a confirmed malicious RubyGems package (MAL-2025-192920) that executes malicious code on install (malicious version 0.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in stripe-backup (RubyGems)

MAL-2025-192920

Immediate action

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

gem uninstall stripe-backup

Malicious versions

1 flagged

0.0.0

Indicators of compromise (SHA-256)

83e6cba910daccd5f8e4800f0aef16bd697b0886993d2fdfdaf5b8d99340b2cc

db992c7aa34404ece8b84a59372fa49fdc08b7db46e38d165061cb5e8d8d7745

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06631RLUA-2026-09466

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks stripe-backup-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