Which versions of wmj167461 are malicious?

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

How do I remediate wmj167461 if I installed it?

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

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

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

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

Malicious package

wmj167461RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9379

Immediate action

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

gem uninstall wmj167461

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ff3fa078213ba07d0ce593e9f1a5e0d71224ea034af87bf4444846920d8b1101

e7bfcbf730c89057c82b3a7c59794d300b472a2eeb6a94c2eda6e6c780273b9c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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