Which versions of wmj557183 are malicious?

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

How do I remediate wmj557183 if I installed it?

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

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

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

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

Malicious package

wmj557183RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9381

Immediate action

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

gem uninstall wmj557183

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6deadc6413f19e61a31ed40615a5099c62f4fd2681c888e5892c10be4c866246

c9a2faf11903ed32f211be10843743bc8b5b70685974bd84983cb92d68c55f7f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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