Which versions of pwnldir1 are malicious?

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

How do I remediate pwnldir1 if I installed it?

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

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

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

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

Malicious package

pwnldir1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8478

Immediate action

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

gem uninstall pwnldir1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

dc6ef22f80130bf75ffbad3a64291e869b6d07b0da6317723e14b8b756400ca8

3a3c4cd683f53397a3311a2c4aa04077e16b877a4eecbf56c90c2183b7068a7a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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