Which versions of lamj02 are malicious?

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

How do I remediate lamj02 if I installed it?

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

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

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

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

Malicious package

lamj02RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7869

Immediate action

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

gem uninstall lamj02

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

042d453c93cf4183f5b21c176f7f1bcbb91b18e7b30551f9d8d7310153c1d682

2d940c4efb570e0c2b19e9876b99b22187b32d4154d38fa302f9dee5b2a69fa5

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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