Which versions of uuext4c477b are malicious?

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

How do I remediate uuext4c477b if I installed it?

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

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

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

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

Malicious package

uuext4c477bRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9035

Immediate action

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

gem uninstall uuext4c477b

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

87237ce68406237a640797eb3ad6c5dd4b8ee79f18b5f88ae2bc76adc9a4ce50

c223ef35362b88ce1f6f9d0b20660630e5b9dc42725d9baca70d3c0c8f1340c7

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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