Which versions of lamnew05 are malicious?

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

How do I remediate lamnew05 if I installed it?

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

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

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

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

Malicious package

lamnew05RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7893

Immediate action

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

gem uninstall lamnew05

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

435203d10c662295c8bc86274eb4da63cd40b35ca2b961628fe2a1737fb42bc4

4c6b2bf79d68afde355707e1ad256f5f6f7e27160d4b7fdaf0f059f77c2df9c6

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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