Which versions of doge-helper are malicious?

The following RubyGems versions of doge-helper are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate doge-helper if I installed it?

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

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

Yes — doge-helper is associated with the RLMA-2024-05672, RLUA-2024-10191, RLUA-2026-08010 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 doge-helper across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for doge-helper (version 0.1).

Malicious package

doge-helperRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

doge-helper is a confirmed malicious RubyGems package (MAL-2024-6866) that executes malicious code on install (malicious version 0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in doge-helper (RubyGems)

MAL-2024-6866

Immediate action

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

gem uninstall doge-helper

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

e97b98c494e0701e72be159188c8b3b72863389bfe06f732631240cc4b58898b

60ab393cd3626492f7ad7c759c2c2534ce4ba65318f00ab6cc8c9dd519dcf979

cfe8e0c45ba5b2a11c6973c7b0cc8cb5386cbb2d441e871f8e6c269e8a79f0e9

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05672RLUA-2024-10191RLUA-2026-08010

References

Credits

ReversingLabs · finder

Detect & block this

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