Which versions of lambprobe4341 are malicious?

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

How do I remediate lambprobe4341 if I installed it?

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

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

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

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

Malicious package

lambprobe4341RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7815

Immediate action

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

gem uninstall lambprobe4341

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

099ddcced5e0fe3bfc125b708c3f68828813504d82a7f80cde8c39f3eb7c0593

91169e1958a703db10cdd1a6ac70221c250d301801f1e52b47d663f1536d1c09

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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