Which versions of lambethssrfbuild are malicious?

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

How do I remediate lambethssrfbuild if I installed it?

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

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

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

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

Malicious package

lambethssrfbuildRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7794

Immediate action

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

gem uninstall lambethssrfbuild

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

4f105ce11e039272e6c1647dc6aee167478382b24136f160d6864979b6d6c40a

97b4a56402de4c9aa1546124730a27b665de389dbca4e182a4d6cdf3287f2a5e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for lambethssrfbuild (2 malicious versions).
If you installed it — respond
Remove lambethssrfbuild 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 lambethssrfbuild 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. lambethssrfbuild 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-02452RLUA-2026-08267

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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