Which versions of lambfetch003 are malicious?

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

How do I remediate lambfetch003 if I installed it?

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

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

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

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

Malicious package

lambfetch003RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7801

Immediate action

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

gem uninstall lambfetch003

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

beb4616b384551440a4d1bd76d229b2e59b48bf41f7ad8e9f1f766b958bd55d1

b3f210b515d48233cf9bc6c8e2fcf21579e94efd8ee459fb3f0fa82e00c0faf7

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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