Which versions of lambfetch001 are malicious?

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

How do I remediate lambfetch001 if I installed it?

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

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

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

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

Malicious package

lambfetch001RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7799

Immediate action

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

gem uninstall lambfetch001

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

50cdbf7d54a7693d7efd256d285611f5f089dff9e12421a121b2f50f0ed518f1

636b6b6827819bffb7a782c946043f1ea3313c2b6101f784b1c992369129efda

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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