Which versions of councilfetchxqz are malicious?

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

How do I remediate councilfetchxqz if I installed it?

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

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

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

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

Malicious package

councilfetchxqzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7603

Immediate action

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

gem uninstall councilfetchxqz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e4c9198ceab83bd949ca6e437541a2f668fb3052b8c2c5734c87dbc31842405e

9f7898e68b2721275046d26426db44b970ee9f69ea92be4a8632c32e38c20822

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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