Which versions of lammcal4 are malicious?

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

How do I remediate lammcal4 if I installed it?

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

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

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

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

Malicious package

lammcal4RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7881

Immediate action

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

gem uninstall lammcal4

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8a30b12df773faf73146303b29eacfe0bc0c7e34873c788505ebe961597c148a

d0f21e58c705e3d5ab483a05133d187634e18d84e7918355e253b1fb35e2ab74

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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