Which versions of lambbzrproxyoai are malicious?

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

How do I remediate lambbzrproxyoai if I installed it?

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

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

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

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

Malicious package

lambbzrproxyoaiRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7785

Immediate action

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

gem uninstall lambbzrproxyoai

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

75ed07cdc951155748b535b290d184fa9f61132e92533d44cea1ec729d75be5e

99eeeaf8637f299cf6fc144ed8a137fbf621aba612b7fa87f6af7cec0d822294

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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