Which versions of xla01778568189 are malicious?

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

How do I remediate xla01778568189 if I installed it?

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

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

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

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

Malicious package

xla01778568189RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9528

Immediate action

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

gem uninstall xla01778568189

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6736a0f1a05cab40d3d8c3cd7a4aa4c516c17de352d18e0090fb97cd58d916f8

a96fc5234cc4a7bf5079d41666168b382be0f791b206084c5db351529567bc3d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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