Which versions of lamtrigger71 are malicious?

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

How do I remediate lamtrigger71 if I installed it?

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

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

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

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

Malicious package

lamtrigger71RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7900

Immediate action

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

gem uninstall lamtrigger71

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

daae6ac9ef81ba450b6391de5f2a4e07b24ecf9356a3519bdb2f25b85500047e

f13ca16443d8298632671e0c6c7dfb95279a0a511657d745477e7603634a5a01

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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