Which versions of pwnlambjan6 are malicious?

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

How do I remediate pwnlambjan6 if I installed it?

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

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

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

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

Malicious package

pwnlambjan6RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8476

Immediate action

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

gem uninstall pwnlambjan6

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

df17a61a8df4b12c77e94079ebc9cc7c8f5f8dc774b7c1cf71be0a45f96a839e

3f66f4dc7da56283e833f66cec9e1164681da627a36d671073ce679edff611c3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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