Which versions of lammeet03 are malicious?

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

How do I remediate lammeet03 if I installed it?

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

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

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

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

Malicious package

lammeet03RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7887

Immediate action

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

gem uninstall lammeet03

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

98106aa1780e64b24822d1f80d40d210b7f7222637dbc1f40dcff938b76b6642

9219d8815d08a50e0d30bf49f2c66d536f8d0828909bfd21d69b90ade7e568ea

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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