Which versions of pd130917vxnt are malicious?

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

How do I remediate pd130917vxnt if I installed it?

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

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

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

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

Malicious package

pd130917vxntRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8413

Immediate action

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

gem uninstall pd130917vxnt

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9900f29b4f4790f774c4173e707078fd818ab91624f156f683bef20151366529

c3ff371180b6dba27939f279bee313119d88f1ce3a8499880d20d6416d9095ef

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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