Which versions of xlambcal1 are malicious?

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

How do I remediate xlambcal1 if I installed it?

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

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

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

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

Malicious package

xlambcal1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9531

Immediate action

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

gem uninstall xlambcal1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2d8c9f780d8133250d7f908316825c5fce8c7808fc2e8d440b0a4a3fe1807395

a115b68116d3df3eeab1785d13191594c46a24f9dd4b6df8a937a71d06658a08

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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