Which versions of cucumber-rake_runner are malicious?

The following RubyGems versions of cucumber-rake_runner are flagged malicious: 0.0.3. Treat any of these as compromised.

How do I remediate cucumber-rake_runner if I installed it?

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

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

Yes — cucumber-rake_runner is associated with the RLMA-2024-05651, RLUA-2024-10170, RLUA-2026-07949 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 cucumber-rake_runner across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for cucumber-rake_runner (version 0.0.3).

Malicious package

cucumber-rake_runnerRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

cucumber-rake_runner is a confirmed malicious RubyGems package (MAL-2024-6845) that executes malicious code on install (malicious version 0.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cucumber-rake_runner (RubyGems)

MAL-2024-6845

Immediate action

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

gem uninstall cucumber-rake_runner

Malicious versions

1 flagged

0.0.3

Indicators of compromise (SHA-256)

942dbc76228f32678ec39b80e3905703a626d81b6c40e1df9abad85dd23e9624

917a7511bdad5eac074264a1d1bfb9324d7df7d15f963b78b2abb5745f4fb3f7

d0ef8b569d3550764dbc7d1cadb750c4d0fc27a222faf64acc8a220c8f0a61b6

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05651RLUA-2024-10170RLUA-2026-07949

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks cucumber-rake_runner-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