Which versions of referral-candy are malicious?

The following RubyGems versions of referral-candy are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate referral-candy if I installed it?

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

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

Yes — referral-candy is associated with the RLMA-2024-05816, RLUA-2024-10337, RLUA-2026-09031 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 referral-candy across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for referral-candy (version 0.1.0).

Malicious package

referral-candyRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

referral-candy is a confirmed malicious RubyGems package (MAL-2024-7011) that executes malicious code on install (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in referral-candy (RubyGems)

MAL-2024-7011

Immediate action

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

gem uninstall referral-candy

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

5a4d0590c1f8b14ef796cdc0c24f16ebdb7ee861aa5b75cc10c3134c7b82166a

6090ff02a0c36bd3e31b9c86409e1e69522276b9c2379fcc3275995914b6ce03

b6bfeed1eda63c53cf7a26a333437cf4c52bf3f1061bb871f41520693a965387

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05816RLUA-2024-10337RLUA-2026-09031

References

Credits

ReversingLabs · finder

Detect & block this

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