Which versions of prof-qux are malicious?

The following PyPI versions of prof-qux are flagged malicious: 0.0.1, 0.0.2, 0.0.3, 0.0.4. Treat any of these as compromised.

How do I remediate prof-qux if I installed it?

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

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

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

Malicious package

prof-quxPyPI

Malicious code in prof-qux (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191821

Immediate action

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

pip uninstall prof-qux

What this malware does

Package silently exfiltrates user's credentials ahead of starting the promised functionality. First batch used simple code, the newer attempt to hide functionality by using compiled modules

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

Campaign: 2025-07-prof-quotex

Reasons (based on the campaign):

action-hidden-in-lib-usage
A Telegram webhook is used to send collected data.
exfiltration-credentials

Malicious versions

4 flagged

0.0.10.0.20.0.30.0.4

Indicators of compromise (SHA-256)

bdc7a9e5c35abee9504343d1d2236e19d23556b4d45370b9c6287d88a8e0e41a

5b87af8d8f13bd43c1cf3490ea551b8d60fe05a482875597ef2fe5d2c200ca19

f02730ba54323a45a43702f72877e2df8b05ce54307980eeebbdc55276856d63

270e21378321e13660721977370c7da51014c1dd03effb85af7bdf736741f6f8

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 prof-qux (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging prof-qux across your stack and pipelines.
If you installed it — respond
prof-qux 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 prof-qux 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 prof-qux 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. prof-qux on PyPI has been identified as a malicious package (versions 0.0.1, 0.0.2, 0.0.3, 0.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-07-prof-quotex

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks prof-qux-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