Which versions of w9927 are malicious?

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

How do I remediate w9927 if I installed it?

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

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

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

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

Malicious package

w9927RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9125

Immediate action

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

gem uninstall w9927

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3db2f2d56a486a478231245eca14d419968257421b77c17e359139736ba7878d

fca93df9304552340e58cd8518997703d6743b5ffa95d04ec4b1160a76d1badb

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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