Which versions of pdatainstaller are malicious?

The following PyPI versions of pdatainstaller are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate pdatainstaller if I installed it?

pdatainstaller is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed pdatainstaller — how do I know if it already compromised me?

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

Yes — pdatainstaller is associated with the 2025-12-pdatainstaller 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 pdatainstaller 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 pdatainstaller (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pdatainstaller across your stack and pipelines.

Malicious package

pdatainstallerPyPI

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

MAL-2026-26

Immediate action

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

pip uninstall pdatainstaller

What this malware does

Package is designed to download and execute a remote script, but the script itself seems to be broken (missing or wrong URLs). It's most probably a test before next packages with real malicious content.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-12-pdatainstaller

Reasons (based on the campaign):

Downloads and executes a remote malicious script.
malware
Downloads and executes a remote executable.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

671a0098c14338197a26cb64b7f5c35c0e741f3151313fff784bc7a4862ad579

43639109001c8715b46aa2fad8a81b420f3d4b0d33f98429a4446a41071fff11

a0f61d7119c73856199e3d68b6a50685c53fbe27a1de18134f9e9d61e239e3cf

00ea1e05067a79da4cbe3d2d1a8a98e7599dc0ef49319046391ca397ceb4730e

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pdatainstaller (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pdatainstaller across your stack and pipelines.
If you installed it — respond
pdatainstaller is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If pdatainstaller 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 pdatainstaller 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. pdatainstaller on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-12-pdatainstaller

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks pdatainstaller-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring