Which versions of lamk03 are malicious?

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

How do I remediate lamk03 if I installed it?

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

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

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

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

Malicious package

lamk03RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7876

Immediate action

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

gem uninstall lamk03

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

27f30292b5d3f4e8cced698070cff8842ea461a30faa0384695387e9c3527b7e

541ca966c67c8349f8d564899bf6438f4b25c0125fedd94608433b464536724b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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