Which versions of lamj01 are malicious?

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

How do I remediate lamj01 if I installed it?

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

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

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

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

Malicious package

lamj01RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7868

Immediate action

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

gem uninstall lamj01

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b294c6c5a5dab4423b2b741b6424fa48ee87aef10bc5df109cdaf7e876818862

e5fa791cc9fbf7d72245c4f5ed57c2df7729eec28a0d50dd7893ecdfa749a178

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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