Which versions of drupal-fu are malicious?

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

How do I remediate drupal-fu if I installed it?

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

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

Yes — drupal-fu is associated with the RLMA-2024-05683, RLUA-2024-10202, RLUA-2026-08021 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 drupal-fu across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for drupal-fu (version 0.0.1).

Malicious package

drupal-fuRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

drupal-fu is a confirmed malicious RubyGems package (MAL-2024-6877) 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 drupal-fu (RubyGems)

MAL-2024-6877

Immediate action

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

gem uninstall drupal-fu

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1a62877585a1c83a9702028d1eeb298cea4bc3d9310ed40499456c1273df4ee7

c8040ce6d7ecece4599a456766406eff2f0377f79e415476094d83c1a77f7106

5962ca7f2754c2804d2390850c656a9025dabaa49869b19028d7a17564f23b96

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for drupal-fu (version 0.0.1).
If you installed it — respond
Remove drupal-fu 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 drupal-fu 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. drupal-fu 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-05683RLUA-2024-10202RLUA-2026-08021

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks drupal-fu-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