Which versions of lammcal6 are malicious?

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

How do I remediate lammcal6 if I installed it?

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

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

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

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

Malicious package

lammcal6RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7883

Immediate action

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

gem uninstall lammcal6

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3ac0c68a4d9f7c6066cdca711a0312f40137a0a989de8b41c5e925e4642da649

418394e85a69faf928b557ba5f717e0ad4dbc25295693dae21fbe31d2416b1a4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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