Which versions of qagwpyrinwn are malicious?

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

How do I remediate qagwpyrinwn if I installed it?

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

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

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

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

Malicious package

qagwpyrinwnRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8494

Immediate action

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

gem uninstall qagwpyrinwn

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

80b8ff8f166224f37fb595647ddcb34db9b01743e40a322fb6a80eba14de472a

541c6553efac2bcbe210306258337a2ab263fb40ccf2fed8751d4a209dfcc3a4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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