Which versions of pwnlambjan5 are malicious?

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

How do I remediate pwnlambjan5 if I installed it?

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

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

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

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

Malicious package

pwnlambjan5RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8475

Immediate action

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

gem uninstall pwnlambjan5

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1207a4a460de56285a454f612755eb53541f874803cb72c0d7e48a26ea8e0081

8754103fe8680e1fe7be627fa74186e38bbac0c458a5fd21fc38c177a0e0d393

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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