Which versions of w10266x are malicious?

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

How do I remediate w10266x if I installed it?

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

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

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

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

Malicious package

w10266xRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9122

Immediate action

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

gem uninstall w10266x

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6ca67cc32a6fb85ec1daa3636aaa53e9a31c5d412dd96d1280b637359552f7e2

e00d541f6e98e4448241a2be3941d0e47a1731fbe0fa33131e51bf81093cb56f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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