Which versions of danger_brakeman are malicious?

The following RubyGems versions of danger_brakeman are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate danger_brakeman if I installed it?

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

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

Yes — danger_brakeman is associated with the RLMA-2024-05660, RLUA-2024-10179, RLUA-2026-07958 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 danger_brakeman across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for danger_brakeman (version 0.0.1).

Malicious package

danger_brakemanRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in danger_brakeman (RubyGems)

MAL-2024-6854

Immediate action

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

gem uninstall danger_brakeman

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8e59cebfc88e4c817f436d8dc9b5bbf53e0cc88e95c30a8dcfd9ebad88613a51

74c7f4a4e5a084f09ec45b9d494f3fe9a1ac798e44fb5220fdb883e48c17ee06

3e48985adc2790142e407bd7417fbac391c61a653a799691bace56fb872c712f

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05660RLUA-2024-10179RLUA-2026-07958

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks danger_brakeman-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