Which versions of rubylove-playing-cards are malicious?

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

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

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

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

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

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

Malicious package

rubylove-playing-cardsRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

rubylove-playing-cards is a confirmed malicious RubyGems package (MAL-2024-7019) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rubylove-playing-cards (RubyGems)

MAL-2024-7019

Immediate action

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

gem uninstall rubylove-playing-cards

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f25a735cc3878a21616ebddbfe88fb16f866ac02c9644728c8363213ae66f014

bc222d50fa412e987cbdb2a82b74a0837926df03218b22280bb38bc5836e89a0

7fbde8c9ee5c1ec63933de23e97d54d59bdc3d604b7efab855883ba922270193

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05824RLUA-2024-10345RLUA-2026-09090

References

Credits

ReversingLabs · finder

Detect & block this

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