Which versions of pwnlambtest4 are malicious?

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

How do I remediate pwnlambtest4 if I installed it?

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

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

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

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

Malicious package

pwnlambtest4RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8477

Immediate action

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

gem uninstall pwnlambtest4

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

51de4c443a25e9661b3033816eea167bfa9033fd3bd79796ce09c1f600f2cc79

259142336dc727f5a8867a31732ac1aaae59275bac2d7e97b9a99cbf7e0ffd89

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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