Which versions of lambfetch002 are malicious?

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

How do I remediate lambfetch002 if I installed it?

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

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

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

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

Malicious package

lambfetch002RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7800

Immediate action

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

gem uninstall lambfetch002

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4d6b86c9e2601213a1a3b448cc3e0fe551438671a280e20c399540c7e084e665

007674835567e62fb889300a679ac259561c522f8b30218ae811891d50f560b1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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