Which versions of execute-with_rescue_with_airbrake are malicious?

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

How do I remediate execute-with_rescue_with_airbrake if I installed it?

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

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

Yes — execute-with_rescue_with_airbrake is associated with the RLMA-2024-05699, RLUA-2024-10218, RLUA-2026-08067 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 execute-with_rescue_with_airbrake across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for execute-with_rescue_with_airbrake (version 0.0.3).

Malicious package

execute-with_rescue_with_airbrakeRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

execute-with_rescue_with_airbrake is a confirmed malicious RubyGems package (MAL-2024-6893) 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 execute-with_rescue_with_airbrake (RubyGems)

MAL-2024-6893

Immediate action

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

gem uninstall execute-with_rescue_with_airbrake

Malicious versions

1 flagged

0.0.3

Indicators of compromise (SHA-256)

641e4593074634e8973d7eb3bf1a0c63162551705f172b96ce9342f6dfc87e62

70233b8964a613d40eb3b3d4b8ac675f7bff2ed82b6c5acf49820af32fd9009d

2edd2b23f74c72442260ce1bbd02732bafb3d3decc7cca58440a0d7eaefa4cdc

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for execute-with_rescue_with_airbrake (version 0.0.3).
If you installed it — respond
Remove execute-with_rescue_with_airbrake 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 execute-with_rescue_with_airbrake 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. execute-with_rescue_with_airbrake 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-05699RLUA-2024-10218RLUA-2026-08067

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks execute-with_rescue_with_airbrake-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