Which versions of ruby-playing_cards are malicious?

The following RubyGems versions of ruby-playing_cards are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate ruby-playing_cards if I installed it?

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

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

Yes — ruby-playing_cards is associated with the RLMA-2024-05823, RLUA-2024-10344, RLUA-2026-09087 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 ruby-playing_cards across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ruby-playing_cards (version 0.0.2).

Malicious package

ruby-playing_cardsRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

ruby-playing_cards is a confirmed malicious RubyGems package (MAL-2024-7018) that executes malicious code on install (malicious version 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ruby-playing_cards (RubyGems)

MAL-2024-7018

Immediate action

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

gem uninstall ruby-playing_cards

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

bc6d644278b07212bc574fef2c81d4a76422e4b6d743a0ddd4ec8a13e0e96958

6293a4bc05f2d4593012d0cf841d64692e896c7d99617f5c16175b9f48f665ca

1eecc46c96e9f4b74387d3e69b30d590e53f04f040137288f1a05ebf3f446ad9

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05823RLUA-2024-10344RLUA-2026-09087

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks ruby-playing_cards-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