Which versions of resque-stuck_queue are malicious?

The following RubyGems versions of resque-stuck_queue are flagged malicious: 0.5.2. Treat any of these as compromised.

How do I remediate resque-stuck_queue if I installed it?

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

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

Yes — resque-stuck_queue is associated with the RLMA-2024-05817, RLUA-2024-10338, RLUA-2026-09033 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 resque-stuck_queue across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for resque-stuck_queue (version 0.5.2).

Malicious package

resque-stuck_queueRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

resque-stuck_queue is a confirmed malicious RubyGems package (MAL-2024-7012) that executes malicious code on install (malicious version 0.5.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in resque-stuck_queue (RubyGems)

MAL-2024-7012

Immediate action

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

gem uninstall resque-stuck_queue

Malicious versions

1 flagged

0.5.2

Indicators of compromise (SHA-256)

add2695301585793226cceccc53b7debb03069ae04ff33b3db00581186a85df8

0af931cfa182c5b428ca86c70d4407e1c8e4980ea5e6ec55e269dc32e6388913

2df2df828680d4d13f6e778cec5f29bc8e506deead7b376b70b094093e17cc48

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05817RLUA-2024-10338RLUA-2026-09033

References

Credits

ReversingLabs · finder

Detect & block this

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