Which versions of w10385x are malicious?

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

How do I remediate w10385x if I installed it?

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

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

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

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

Malicious package

w10385xRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9124

Immediate action

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

gem uninstall w10385x

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

38e64b6495f45bfdeda6d620c87c4bbb061791153d4dc2f5850b75536509b459

38d400ba881da8a474d45f7f0558219dc947778ced2e75ee00b587b50b95d59f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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