Which versions of g8402gqdyg are malicious?

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

How do I remediate g8402gqdyg if I installed it?

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

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

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

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

Malicious package

g8402gqdygRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7703

Immediate action

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

gem uninstall g8402gqdyg

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d4afc2c07bab24d8920fdd32cadacfd7212303fc124ad19204e2f97f838c274b

d6a772b119b1443fd209c9f0b2d7044db712651cd3713264321dc95ae8663c5a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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