Which versions of lambpxnew14300 are malicious?

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

How do I remediate lambpxnew14300 if I installed it?

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

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

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

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

Malicious package

lambpxnew14300RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7833

Immediate action

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

gem uninstall lambpxnew14300

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4df69dbd95d489da01771b768e37f262318d39b14945e37322f1ec121f8a73c4

b95e5e99156de28dd37bed7a3120db8124c61093b2632cac1144730ebef93684

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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