Which versions of lamdoc17474 are malicious?

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

How do I remediate lamdoc17474 if I installed it?

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

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

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

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

Malicious package

lamdoc17474RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7859

Immediate action

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

gem uninstall lamdoc17474

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a087953bb5d947a28333fdbea576fdd31940c1931d5bc268572b737fadb2371d

bb71e4985f03fe93bad0126462c71f5185301b6303d8a67cfc3f74ec3a98d6bb

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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