Which versions of lamj03 are malicious?

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

How do I remediate lamj03 if I installed it?

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

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

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

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

Malicious package

lamj03RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7870

Immediate action

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

gem uninstall lamj03

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

514fcffeffd01abe892521ccb5fcb79cf421926538d7e14acb45656e6a28aa99

07710e80a796d4c17f5b47ec4849a38366dd9ce7862816449a450266ff481385

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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