Which versions of pwnlambcal2 are malicious?

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

How do I remediate pwnlambcal2 if I installed it?

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

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

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

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

Malicious package

pwnlambcal2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8471

Immediate action

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

gem uninstall pwnlambcal2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4ea69783f9e0de2ce61e8d832cd25ac456f85b266ce61b2e54648be8ceb5aa4e

29309b5e11dc54a8497129f2eaf3ba5403958b7a5fc57dac1ff747cdac849570

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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