Which versions of lambcal434a2 are malicious?

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

How do I remediate lambcal434a2 if I installed it?

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

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

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

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

Malicious package

lambcal434a2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7787

Immediate action

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

gem uninstall lambcal434a2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

39efbcd30dde02106873dcee6f110673311589647efa8e84aafe05c06850b536

091e910d00f9ec173214277c5822c55ad9e651f7bd8bf1ecedb506d6c7774b24

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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