Which versions of lammcal5 are malicious?

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

How do I remediate lammcal5 if I installed it?

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

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

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

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

Malicious package

lammcal5RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7882

Immediate action

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

gem uninstall lammcal5

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c4120917a5a983a6a4ec5872f47a7051285c460e440fcfac1577c1d193efe4db

22e60334f74a8851f1bbf9c5db5604aafc16a2ca15f59de9a5d61cf9c0da4213

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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