Which versions of lammeet02 are malicious?

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

How do I remediate lammeet02 if I installed it?

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

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

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

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

Malicious package

lammeet02RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7886

Immediate action

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

gem uninstall lammeet02

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2288751701b3569c0faa2ac4240ef04d2760b6808b5f637e02d1ba89cb808d96

3373cbe1ec1c58541786a56229c1da385965fd99fefc08378629fe285e9fe29d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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