Which versions of zrgvq116b are malicious?

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

How do I remediate zrgvq116b if I installed it?

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

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

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

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

Malicious package

zrgvq116bRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9735

Immediate action

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

gem uninstall zrgvq116b

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5b4a8da275e00dd5349fc780e9f671de7b7a8435773900e74ff38c992222db05

715ff883f2b274c78dece70b8835c51c16025d07e6052063b2eb71f92a79fa3a

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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