Which versions of lamdoc17451 are malicious?

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

How do I remediate lamdoc17451 if I installed it?

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

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

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

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

Malicious package

lamdoc17451RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7857

Immediate action

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

gem uninstall lamdoc17451

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8f12569f1c3e6b19fd645f1c30e8c494a3e9ec98026113e55233cb3205920ca9

016053d059d31e40a09ce1f3a51ca1a9674c09a28b7687555718ad6d0b7c22cb

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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