Which versions of qagfypuewln are malicious?

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

How do I remediate qagfypuewln if I installed it?

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

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

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

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

Malicious package

qagfypuewlnRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8486

Immediate action

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

gem uninstall qagfypuewln

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

acffc97ee683eb4b36693c2e0e6b14db48c3c076f1fad9f14128d85fd9f5b717

c14f6d29d1a3f3eb516d6050ccc691269a37f1e775b120fc86e8468861b09a8d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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