Which versions of pwnwtest1 are malicious?

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

How do I remediate pwnwtest1 if I installed it?

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

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

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

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

Malicious package

pwnwtest1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8480

Immediate action

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

gem uninstall pwnwtest1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

86923c06f687df9d0874f620829e00cca539340c6651c51a6ff39367da980675

d1a08bc138c8d6dffcfcbee7e536bc3bb7fc594a47553856b8cd4493eef9dfb7

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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