Which versions of lambethtestdef are malicious?

The following RubyGems versions of lambethtestdef are flagged malicious: 0.0.54890. Treat any of these as compromised.

How do I remediate lambethtestdef if I installed it?

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

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

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

Search your lockfiles and build artifacts for lambethtestdef (version 0.0.54890).

Malicious package

lambethtestdefRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

lambethtestdef is a confirmed malicious RubyGems package (MAL-2026-7797) that executes malicious code on install (malicious version 0.0.54890). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in lambethtestdef (RubyGems)

MAL-2026-7797

Immediate action

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

gem uninstall lambethtestdef

Malicious versions

1 flagged

0.0.54890

Indicators of compromise (SHA-256)

32cb5e2aff0e783323d1b6658420efbc8b626b757cabd9e480162128c5880f51

c544ee1fcc46b1807cd53deab02646886c4afa481d8a1e1346d8188787d4c424

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02455RLUA-2026-08270

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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