Which versions of w9927x are malicious?

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

How do I remediate w9927x if I installed it?

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

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

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

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

Malicious package

w9927xRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9126

Immediate action

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

gem uninstall w9927x

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

befc30dfe8ba4c0d67da3e53a328859af9824208e14022a7c80414444192e346

b1785eda61687c98eb1aeaafa66abe2cd799402d2c011895ab95dcba0dcad324

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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