Which versions of pdsuax are malicious?

The following PyPI versions of pdsuax are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate pdsuax if I installed it?

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

If pdsuax was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is pdsuax part of a known attack campaign?

Yes — pdsuax is associated with the RLMA-2024-08668 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 pdsuax across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pdsuax (version 0.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pdsuax across your stack and pipelines.

Malicious package

pdsuaxPyPI

Malicious code in pdsuax (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-10101

Immediate action

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

pip uninstall pdsuax

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

9b9484e0227809f54e2e399c7d35fc08f2e49daa7a885a2f0a87cedd8c3ca596

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pdsuax (version 0.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pdsuax across your stack and pipelines.
If you installed it — respond
Remove pdsuax 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 pdsuax was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks pdsuax before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. pdsuax on PyPI has been identified as a malicious package (version 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-08668

Credits

ReversingLabs · finder

Detect & block this

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

pdsuaxPyPI

Malicious versions

Indicators of compromise (SHA-256)

Detection & response playbook

Find it

If you installed it — respond

Did it already run?

How O3 protects you

Frequently asked questions

Campaign

Credits

Detect & block this