Which versions of lambsvnproxyoai are malicious?

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

How do I remediate lambsvnproxyoai if I installed it?

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

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

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

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

Malicious package

lambsvnproxyoaiRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7843

Immediate action

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

gem uninstall lambsvnproxyoai

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

fc9daae1f0dd637c765d42406ecfbe79b6df2e72f59540a35b105574e8084d1e

8482728c0dd83db7048de1d9b57d75b99243e835c7f726ed66b945dc916e4ae0

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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