Which versions of pd131119hccc are malicious?

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

How do I remediate pd131119hccc if I installed it?

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

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

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

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

Malicious package

pd131119hcccRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8420

Immediate action

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

gem uninstall pd131119hccc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

cadeee27926508fe53d64c0774197029f5240e8980ac2699fd4707c1bed93240

24076a8c33e37b5def89d66e0b54f439f7f8312f948393aba8eb8be78acf2595

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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