Which versions of w10385 are malicious?

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

How do I remediate w10385 if I installed it?

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

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

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

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

Malicious package

w10385RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9123

Immediate action

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

gem uninstall w10385

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e043ce3a803a42cceaa3d358e3dc97f03fb44614ff95346304101a03836656e4

41c5da6709a00fd4aebf4ff1a9f846719640260490371aec16399d5cc0b6ed72

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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