Which versions of wmj738682 are malicious?

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

How do I remediate wmj738682 if I installed it?

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

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

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

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

Malicious package

wmj738682RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9382

Immediate action

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

gem uninstall wmj738682

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5bf47fafaca019764d4df6bf62ff5a614695076f814b64c27fbc63b2ed3cf695

699fbbe63b64925ff6a00206b6e40cd904516bf41dc902fdba465f33d521fd16

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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