Which versions of lambprobe7763 are malicious?

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

How do I remediate lambprobe7763 if I installed it?

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

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

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

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

Malicious package

lambprobe7763RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7819

Immediate action

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

gem uninstall lambprobe7763

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

fee8e8026851fb676ed90cb9d0fd7c19dbf0049e79e0bd9b212d9ba18177eb97

47a48aa98c7aa59834c2031e275410f8416fa6ad60f63417b01c55865186853c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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