Which versions of prof-tg-gdghho-qu are malicious?

The following PyPI versions of prof-tg-gdghho-qu are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate prof-tg-gdghho-qu if I installed it?

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

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

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

Malicious package

prof-tg-gdghho-quPyPI

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

MAL-2025-191825

Immediate action

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

pip uninstall prof-tg-gdghho-qu

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

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2c008fd8741f0aed698d5b2c4799ac047bff1cc1c5a0fc37faaff1248fb113c1

6df3141fefe81c96a851af6c8844be2deba7f120c5700fed083ef85087a132b0

98296856c5c09fec72255a4bee01bded436e274913ac54172974bf0ae18dc2d1

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-tg-gdghho-qu (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging prof-tg-gdghho-qu across your stack and pipelines.
If you installed it — respond
prof-tg-gdghho-qu 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-tg-gdghho-qu 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-tg-gdghho-qu 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-tg-gdghho-qu on PyPI 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

2025-07-prof-quotex

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks prof-tg-gdghho-qu-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