Which versions of lamk02 are malicious?

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

How do I remediate lamk02 if I installed it?

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

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

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

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

Malicious package

lamk02RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7875

Immediate action

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

gem uninstall lamk02

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5b5f554c72bab4a77d76abeb60a7524f704705881ecdd996bd9ae35a535938da

31ac36b783f6f5632540f86b8b3dad57d82311422242b9e631e587b2ebf20d71

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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