Which versions of lambfetch005 are malicious?

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

How do I remediate lambfetch005 if I installed it?

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

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

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

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

Malicious package

lambfetch005RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7803

Immediate action

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

gem uninstall lambfetch005

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e42e32fff52ed1f6dc13bff1cc7d782eba728532050172354ac6a188972064e9

d11e98da8f2dd86db61d1da8eec0f6e29d0e471a41c396458b7b38a125bae65f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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