Which versions of lambcal434a1 are malicious?

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

How do I remediate lambcal434a1 if I installed it?

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

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

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

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

Malicious package

lambcal434a1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7786

Immediate action

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

gem uninstall lambcal434a1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a95080414730a1b49bee6545728ae867c174edc85ddc7f232bda22a54fd55a80

b10b70cb41f01b9371017298f276d347bbe993829f7bdc68fe1b2bef25419e16

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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