Which versions of wmj169905 are malicious?

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

How do I remediate wmj169905 if I installed it?

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

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

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

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

Malicious package

wmj169905RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9380

Immediate action

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

gem uninstall wmj169905

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

04a231f40af96dd3903b7a774f974b2664441de60967662bdb66f16792b08b27

b9929f8818a64ccbb52acd912542e8313b0af22211dadd358ef51bba412c14a8

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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