Which versions of lamk04 are malicious?

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

How do I remediate lamk04 if I installed it?

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

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

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

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

Malicious package

lamk04RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7877

Immediate action

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

gem uninstall lamk04

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4f1446ebe2ed1174b085e1785460b21c83fd68ae47a5629963e75506698dd668

5021f6a2c48f481cf8ae6553b922a53639ed6ddb3140be6d195c82fd1ff24a8b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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