Which versions of playing-cards are malicious?

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

How do I remediate playing-cards if I installed it?

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

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

Yes — playing-cards is associated with the RLMA-2024-05810, RLUA-2024-10331, RLUA-2026-08948 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 playing-cards across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for playing-cards (version 0.0.2).

Malicious package

playing-cardsRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

playing-cards is a confirmed malicious RubyGems package (MAL-2024-7004) 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 playing-cards (RubyGems)

MAL-2024-7004

Immediate action

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

gem uninstall playing-cards

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

22d1ec2bd6095e07c29b3c98787545740b6e2163e9879ca617418260dd60c056

c5da9cd704c55ff92c47fd94c71fe3661ae8b8d1af25fe692f2f30b6fd6c912e

1db215a32e69c121bd6db212eb31c9c5f0744c8e8c3fac07587235e1bed93b4d

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for playing-cards (version 0.0.2).
If you installed it — respond
Remove 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 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. 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-05810RLUA-2024-10331RLUA-2026-08948

References

Credits

ReversingLabs · finder

Detect & block this

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