Which versions of wm961055 are malicious?

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

How do I remediate wm961055 if I installed it?

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

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

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

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

Malicious package

wm961055RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9377

Immediate action

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

gem uninstall wm961055

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

426b2b57fa29fac383ab4f34f0db7e0a82728dfd4c0aaa8ed1b508c5534849bc

253f02dc82d7dfa40c81c92ed3cfdbc9c1ee4297417012e141503f55dfb93072

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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