Which versions of wm720979 are malicious?

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

How do I remediate wm720979 if I installed it?

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

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

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

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

Malicious package

wm720979RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9374

Immediate action

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

gem uninstall wm720979

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f8c00d6f6640d70f863803b8c2803e978d1f9410d0e92e669f620707190385be

bdd0bc8dac98a53fda115c1b33a752ce3e75e8bf3a736c8f2126a5e96cc78650

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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