Which versions of pd130924vejy are malicious?

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

How do I remediate pd130924vejy if I installed it?

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

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

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

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

Malicious package

pd130924vejyRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8414

Immediate action

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

gem uninstall pd130924vejy

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8bfd500743ea861dafaf069e60261721ad10e10ebce521564727988c56f6ea4a

3469accb493d2a50274a6fa70a8e71c98b53ccf6f625355b62c0d9a9e3f98e42

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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