Which versions of quizdom are malicious?

The following PyPI versions of quizdom are flagged malicious: 0.1.0, 0.2.0, 0.3.0. Treat any of these as compromised.

How do I remediate quizdom if I installed it?

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

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

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

Malicious package

quizdomPyPI

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

MAL-2025-3208

Immediate action

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

pip uninstall quizdom

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

The OpenSSF Package Analysis project identified 'quizdom' @ 0.1.0 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

3 flagged

0.1.00.2.00.3.0

Indicators of compromise (SHA-256)

54859476f6015ea4a22d1cbfaf5087feddc5a7281f40482da9fd9cb7aa362f65

9b43ffb1ee6cbcdc7b9b8a0c2e37c763acc65e97e85e69a991c8c936069dc59e

645c3cc942152f460230ac5477b10e0845893c83751f26d5d4327e7d938e5fb4

2b6e87a0fb56928d5946cb4cff73f2dd9a9ef6eda0d943f74d7f0c4333df8be0

b84a7ac7e82cf445e341d1278c6cfd9b9e7b11a5010fbe65bfbe5bd430a668c4

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

Campaign

GENERIC-standard-pypi-install-pentest

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder

Detect & block this

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