Which versions of civichookfake are malicious?

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

How do I remediate civichookfake if I installed it?

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

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

Yes — civichookfake is associated with the RLMA-2026-02253, RLUA-2026-07931 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 civichookfake across my projects, lockfiles, and CI pipelines?

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

Malicious package

civichookfakeRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

civichookfake is a confirmed malicious RubyGems package (MAL-2026-7602) 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 civichookfake (RubyGems)

MAL-2026-7602

Immediate action

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

gem uninstall civichookfake

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a6d72cedd9940523053fe48b49a7df5e93f510b858fc710d4a11a00e7910d1c5

89959fb2edd9e79e98b0a8ff362089837ecee923bad8acc69f2c0575900eef24

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for civichookfake (version 0.0.1).
If you installed it — respond
Remove civichookfake 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 civichookfake 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. civichookfake 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-2026-02253RLUA-2026-07931

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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