Which versions of lamk01 are malicious?

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

How do I remediate lamk01 if I installed it?

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

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

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

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

Malicious package

lamk01RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7874

Immediate action

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

gem uninstall lamk01

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

34eca83fa3fee0dc8687051ca96f66b4672e09fd21c49619570c083f3f7a6a7b

c196a43881a89547e4eb4ed1e6e98ae2551788a4428da64abc0b06762514bb79

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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