Which versions of stripe-server are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for stripe-server (version 0.2.15).

Malicious package

stripe-serverRubyGems

Advisory published Dec 23, 2025Updated Sep 24, 2026

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

Malicious code in stripe-server (RubyGems)

MAL-2025-192922

Immediate action

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

gem uninstall stripe-server

Malicious versions

1 flagged

0.2.15

Indicators of compromise (SHA-256)

4771b0087ba742fe5490a1ebe68203c251fdc412d0afb84de5e2970e523030f9

1d4ee14e88f95b49f7d3adb2ebb1fd457e3f815fce8e30a707c1662191779424

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06633RLUA-2026-09468

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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