Which versions of lamdoc17385 are malicious?

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

How do I remediate lamdoc17385 if I installed it?

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

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

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

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

Malicious package

lamdoc17385RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7855

Immediate action

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

gem uninstall lamdoc17385

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ef40937912f1032e9b4888e35adb871dbbb10253cfc642ef3bbefc78a8661238

8613b9ef0866202be908ed62af0d3891fe240ed917c55a652b4f5c7a077813f4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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