Which versions of qagpujyfgjw are malicious?

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

How do I remediate qagpujyfgjw if I installed it?

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

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

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

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

Malicious package

qagpujyfgjwRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8490

Immediate action

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

gem uninstall qagpujyfgjw

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

09e4330446ddc0b787b6fc92a31433e6bdf2cac8580124df0f56cec7f56d0ea6

598ff5f741d758b0354e76605df112af2b40a75e0daae53909aa8c087e43a330

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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