Which versions of lammcal1 are malicious?

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

How do I remediate lammcal1 if I installed it?

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

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

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

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

Malicious package

lammcal1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7880

Immediate action

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

gem uninstall lammcal1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b135a38720c1232478701e26bce72e14e5960de02e2677272ba4bda2697c4d31

fbc82cf61eea3e04979aa048b5f4b09e935cb97ae2cc26ba6601f6ff99c5c9cc

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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