Which versions of wm735526 are malicious?

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

How do I remediate wm735526 if I installed it?

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

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

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

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

Malicious package

wm735526RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9375

Immediate action

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

gem uninstall wm735526

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a679f219e10428a86ce414d8612b0cf954ea7aca8ba9464d9c41cb83762ea71c

ea32f029e8281e492bdd44eb0faf7f6e79a75ab88cf6d894b43d3a6161c910a5

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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