Which versions of lambethssrfcal are malicious?

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

How do I remediate lambethssrfcal if I installed it?

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

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

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

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

Malicious package

lambethssrfcalRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7795

Immediate action

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

gem uninstall lambethssrfcal

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7aed2584e72b5f89ca566b1ce4a9c4e9474849ec736dc14264c97a930a40f89c

08f20fe8173229cb9d2ae3b91b15a8c7bc4a72cd8f8d818d7a96a206caaad723

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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