Which versions of x51a3db3814 are malicious?

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

How do I remediate x51a3db3814 if I installed it?

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

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

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

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

Malicious package

x51a3db3814RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9518

Immediate action

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

gem uninstall x51a3db3814

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

44e30a0e8437733becea945507e8f498cdffff565847a2fca6a694458e4ba6c6

72989d1cfef3a704966dc82bc71d6b55d67bcd6fc184e4bcba0c2e1460f3c8be

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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