Which versions of lambprobe4340 are malicious?

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

How do I remediate lambprobe4340 if I installed it?

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

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

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

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

Malicious package

lambprobe4340RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7814

Immediate action

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

gem uninstall lambprobe4340

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0ff68a2a448aa6f680e5904e0ae845a333a503612b67025e24a72458c9805e75

bc6c9b432ee895f349c0ad0e0b5faec11d3d584b2a7f39a32e83e001526ed5b3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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