Which versions of lamlove2 are malicious?

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

How do I remediate lamlove2 if I installed it?

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

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

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

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

Malicious package

lamlove2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7879

Immediate action

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

gem uninstall lamlove2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

308eb80a4f5fe91ae1a0da712c57007623d3b7233807d44aee2c6437ed66523c

6e884a5b0d66f083d33390a5df88dcabfb8ce12fab3e42fcee2dc0554b5c8445

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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