Which versions of whg1778555572981 are malicious?

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

How do I remediate whg1778555572981 if I installed it?

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

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

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

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

Malicious package

whg1778555572981RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9353

Immediate action

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

gem uninstall whg1778555572981

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

756c3156cdc5c1c9ddd6e0eb037cfc9655e3724144103e79235367aa74c50d2d

fe545970df2e44bfeff87a7d4c5d296d225e7c7a6946d89e7f1d87c177ea3290

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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