Which versions of qagehndongu are malicious?

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

How do I remediate qagehndongu if I installed it?

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

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

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

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

Malicious package

qagehndonguRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8484

Immediate action

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

gem uninstall qagehndongu

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

978ce0e8489f6548bb1d8c25f6f2d3b742bf76001bb43b8cdb3bf5387d28ce55

072cda579c66e6694a85bf4fe07ae85a93a59805cba27dbb5d1766f827b33f0d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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