Which versions of zwpdfg10266b are malicious?

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

How do I remediate zwpdfg10266b if I installed it?

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

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

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

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

Malicious package

zwpdfg10266bRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9895

Immediate action

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

gem uninstall zwpdfg10266b

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

04f30354de1f76684d99e097f75d4145f6e116362a7c41a2d620d0b97fc46b8f

1eed7d26d7aacdc11a0a1ece93e3e5f3c3924530372d4e6b28ab900aac8707b2

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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