Which versions of qagfoukolga are malicious?

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

How do I remediate qagfoukolga if I installed it?

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

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

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

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

Malicious package

qagfoukolgaRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8485

Immediate action

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

gem uninstall qagfoukolga

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

84cf8c806f8943f4e1fed3a4bed27f18a28a287253edadf3f9e8c5edd7f50dd9

985c6e31b298e9f08ad2a7b8340c5a6d2ef0ed03c0c97ece54dfa4456a122809

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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