Which versions of qdatainstaller are malicious?

The following PyPI versions of qdatainstaller are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate qdatainstaller if I installed it?

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

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

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

Malicious package

qdatainstallerPyPI

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

MAL-2026-27

Immediate action

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

pip uninstall qdatainstaller

What this malware does

Package is designed to download and execute a remote script, which then downloads and runs a malicious executable

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.1

Indicators of compromise (SHA-256)

e4ee574ced05e27b63477cb84af816e02ae259c67246f4f31ff63819e7e1048e

2076720ad37488ab7134540a250654eb89997ef874f7833195e7f70cb5a2313d

cbc86a446df2446857043ecf71285623cf05d5fc76bc1185835fc090440166be

fba20822ab0c90405242a5fa9147d5748b78c6d2cca8adf30de03263034da26f

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 qdatainstaller (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging qdatainstaller across your stack and pipelines.
If you installed it — respond
qdatainstaller 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 qdatainstaller 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 qdatainstaller 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. qdatainstaller on PyPI has been identified as a malicious package (version 1.0.1 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 qdatainstaller-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