Which versions of lp256 are malicious?

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

How do I remediate lp256 if I installed it?

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

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

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

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

Malicious package

lp256RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8037

Immediate action

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

gem uninstall lp256

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ed7a9a2107f2709d03d18013b8adad3b681023937ae7ff2807a27fa5b3852233

6f7ee316e62732b247f23bdc7c39095221041c1fd1fa7ea68ad7b5b0d956a75e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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