Which versions of lamj00 are malicious?

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

How do I remediate lamj00 if I installed it?

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

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

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

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

Malicious package

lamj00RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7867

Immediate action

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

gem uninstall lamj00

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

29e55d7cb47c7f7e6f5085a16262a47b2bf5c1655e9293a1d31552ea099e3bd0

cd63f1682b68a76a60be6328d1baf8486a0a6b33b266db8e53f2cd1e04b57596

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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