Which versions of lamhgdemo17360 are malicious?

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

How do I remediate lamhgdemo17360 if I installed it?

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

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

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

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

Malicious package

lamhgdemo17360RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7864

Immediate action

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

gem uninstall lamhgdemo17360

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f7a654e2e1dcfe6dd3c6798f7fe38b0540e2692c8d831cb50711d4cb7477139a

9fc46f3886de8b43043f004854fcda4cb629c88ea176aab2a035fbcdcb022ea4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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