Which versions of lp332 are malicious?

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

How do I remediate lp332 if I installed it?

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

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

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

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

Malicious package

lp332RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8039

Immediate action

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

gem uninstall lp332

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d7acf869e7eb6f4d302ed157b556b07032af9179584882130a811d5645882664

fc2517a49ee9adf75142de851dad5a985a765a580ca648bf857f25b7542a5318

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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