Which versions of lambproxjanb are malicious?

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

How do I remediate lambproxjanb if I installed it?

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

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

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

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

Malicious package

lambproxjanbRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7821

Immediate action

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

gem uninstall lambproxjanb

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f4b0bb744bf90abac2ac5a2cb6f9762a2dd89a07d418703dece6398ba1c37afe

f6a86d45cf54759114b077f3a0948d9ac2b47198b6eac26854bc6443c7714b06

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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