Which versions of wlamhg are malicious?

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

How do I remediate wlamhg if I installed it?

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

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

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

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

Malicious package

wlamhgRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9372

Immediate action

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

gem uninstall wlamhg

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5d92d1273aae509e65ca2367d2405f53cd65ab59e56f16a43a1832acdcf1d46f

d79969c798505d9961a113228e0cb3e8ca3c62125f4b1f3daaae9133d9ea3c39

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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