Which versions of questpro are malicious?

The following PyPI versions of questpro are flagged malicious: 1.0.0, 1.0.3, 3.0.0, 3.0.5, 4.0.0. Treat any of these as compromised.

How do I remediate questpro if I installed it?

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

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

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

Malicious package

questproPyPI

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

MAL-2026-936

Immediate action

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

pip uninstall questpro

What this malware does

When using the package, user's Discord tokens are silently exfiltrated.

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

Campaign: 2026-02-questpro

Reasons (based on the campaign):

infostealer
exfiltration-credentials
action-hidden-in-lib-usage

Malicious versions

5 flagged

1.0.01.0.33.0.03.0.54.0.0

Indicators of compromise (SHA-256)

be333f6f44c50eba4d7a7c11754e048bdc2ed092ae58cee1e88cb24225d4d151

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

Campaign

2026-02-questpro

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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