Which versions of zq17991 are malicious?

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

How do I remediate zq17991 if I installed it?

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

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

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

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

Malicious package

zq17991RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9695

Immediate action

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

gem uninstall zq17991

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2dfb5930457eb0b5ef7cde51e5dfb29f607b206be4fd476be9cb243940b1a9fa

f0e580f9866e8b20b50a367b780c97e90db20449fc564a96c30596ef87a3db6f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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