Which versions of dradis_brakeman are malicious?

The following RubyGems versions of dradis_brakeman are flagged malicious: 3.15.0. Treat any of these as compromised.

How do I remediate dradis_brakeman if I installed it?

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

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

Yes — dradis_brakeman is associated with the RLMA-2024-05677, RLUA-2024-10196, RLUA-2026-08015 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 dradis_brakeman across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dradis_brakeman (version 3.15.0).

Malicious package

dradis_brakemanRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in dradis_brakeman (RubyGems)

MAL-2024-6871

Immediate action

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

gem uninstall dradis_brakeman

Malicious versions

1 flagged

3.15.0

Indicators of compromise (SHA-256)

f3c34cfff2e094550c2a2fa6ea773f5e6dd050bbea8b556da1d5638fae2297a9

6474d5a48a7174edff1245ccf85420b645beacffd1810090a707fe2dc5e1e98a

9539dd400ebf652c46334cafd23dc9ac08f203ed392ccd50b036a58975050c32

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05677RLUA-2024-10196RLUA-2026-08015

References

Credits

ReversingLabs · finder

Detect & block this

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