Which versions of hack-cards are malicious?

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

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

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

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

Yes — hack-cards is associated with the RLMA-2024-05744, RLUA-2024-10263, RLUA-2026-08170 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 hack-cards across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for hack-cards (version 0.0.4).

Malicious package

hack-cardsRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in hack-cards (RubyGems)

MAL-2024-6938

Immediate action

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

gem uninstall hack-cards

Malicious versions

1 flagged

0.0.4

Indicators of compromise (SHA-256)

d3d30e1572f37e0817c2fe184b46bcb97914778ac786718cacddcd183940e5fa

b43979caef418691752805bd69373a108f8410c0715b2937a993da9b88e55a3a

ccfec6c8a242eeb8a6dea81f36419a0e1625a5810fcb49d6ef95b5161d6a3b64

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05744RLUA-2024-10263RLUA-2026-08170

References

Credits

ReversingLabs · finder

Detect & block this

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