Which versions of lamj04 are malicious?

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

How do I remediate lamj04 if I installed it?

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

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

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

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

Malicious package

lamj04RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7871

Immediate action

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

gem uninstall lamj04

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a31cb7dcd8d124ac934cdf496cd8d098e0c656843ddd11e7ae75a8406f671706

993fa67c91b06c71eed06a28d3a67dd23820751f4a55072c26cf10b225647205

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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