Which versions of qageegqgmnk are malicious?

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

How do I remediate qageegqgmnk if I installed it?

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

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

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

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

Malicious package

qageegqgmnkRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8483

Immediate action

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

gem uninstall qageegqgmnk

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d66f4a6be9d59d9549319d686ad1e9745857c466eb520012ae269ed7a5120c3f

d29316575f97bf37b4cafae1feef8b21008c063fedf9da65eeeeff1779366ed2

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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