Which versions of xla11778568189 are malicious?

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

How do I remediate xla11778568189 if I installed it?

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

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

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

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

Malicious package

xla11778568189RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9529

Immediate action

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

gem uninstall xla11778568189

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5f7b5a453bb0caf5ae2620e2ce24b57c183a98ea7d8a6175bd0176592bcf9748

53dbf7ae5b861dd1f945d0c4a70af2a22f5c2d3e25eef5c35ab2b765be807e9a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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