Which versions of dragonfly_activerecord are malicious?

The following RubyGems versions of dragonfly_activerecord are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate dragonfly_activerecord if I installed it?

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

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

Yes — dragonfly_activerecord is associated with the RLMA-2024-05680, RLUA-2024-10199, RLUA-2026-08018 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 dragonfly_activerecord across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dragonfly_activerecord (version 1.0.0).

Malicious package

dragonfly_activerecordRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in dragonfly_activerecord (RubyGems)

MAL-2024-6874

Immediate action

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

gem uninstall dragonfly_activerecord

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

b078464ef1a3a2a04aaa907f9144d708cb9268950ef804f0ce320d31d30e0a59

daf7321b058d5c1746964eaaf6f565241d20c5ac3b9e926da84c5f641ff4dbf5

84fe14487545a41355a61169b9d70eb8cd37f770c7f31b8f44f8d4d18ee26407

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05680RLUA-2024-10199RLUA-2026-08018

References

Credits

ReversingLabs · finder

Detect & block this

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