Which versions of lamdoc17395 are malicious?

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

How do I remediate lamdoc17395 if I installed it?

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

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

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

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

Malicious package

lamdoc17395RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7856

Immediate action

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

gem uninstall lamdoc17395

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

355fc660d19b97ad2ac28c675e81770e93691c7bbd7f408dcca71b27e43e3af7

a61adc3d33b1dd6d1a530b94e85b91bf70ffba119a061748f3b24d1a7fae4e9a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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