Which versions of pwnlambcal3 are malicious?

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

How do I remediate pwnlambcal3 if I installed it?

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

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

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

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

Malicious package

pwnlambcal3RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8472

Immediate action

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

gem uninstall pwnlambcal3

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

42143e8fd4a927bb54c9248b76c74165880a9cc1f1882609de35ecd09d600665

5f5a9ee2a38b3746999d987eef63b4714924ed122b06e16b168d8550f3587f2c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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