Which versions of pd130931tmbp are malicious?

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

How do I remediate pd130931tmbp if I installed it?

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

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

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

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

Malicious package

pd130931tmbpRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8415

Immediate action

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

gem uninstall pd130931tmbp

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6ab2103e12cefb20d60c37081bc4b8ccefda20a06e5666a094e438e86783304e

8eb17243132fc16cb079eb666258d4777ac08afe13d0e38a88727cb178aabe32

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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