Which versions of lammeet01 are malicious?

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

How do I remediate lammeet01 if I installed it?

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

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

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

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

Malicious package

lammeet01RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7885

Immediate action

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

gem uninstall lammeet01

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

67bd59da138d145530315b3be63148bc5088524babf3e8399a23fdbc5420d6b6

c13dbac07a257b916c716d68879759d40d8b7b2229a1082336ab527f76769bb9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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