Which versions of lambethssrfhack are malicious?

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

How do I remediate lambethssrfhack if I installed it?

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

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

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

Search your lockfiles and build artifacts for lambethssrfhack (2 malicious versions).

Malicious package

lambethssrfhackRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

lambethssrfhack is a confirmed malicious RubyGems package (MAL-2026-7796) that executes malicious code on install (malicious versions 0.0.1, 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in lambethssrfhack (RubyGems)

MAL-2026-7796

Immediate action

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

gem uninstall lambethssrfhack

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

57a160119eb8d5235ad563ddcee887f197a6d8f1a277302acabc7dd5d0f9d3eb

c52d533ee297687382d84ef99bd273894529d9ac5939966713a1b7b3ae32dd28

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for lambethssrfhack (2 malicious versions).
If you installed it — respond
Remove lambethssrfhack 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 lambethssrfhack 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. lambethssrfhack on RubyGems has been identified as a malicious package (versions 0.0.1, 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-02454RLUA-2026-08269

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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