Which versions of christmasmiraclemaker are malicious?

The following PyPI versions of christmasmiraclemaker are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate christmasmiraclemaker if I installed it?

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

If christmasmiraclemaker was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is christmasmiraclemaker part of a known attack campaign?

Yes — christmasmiraclemaker is associated with the 2023-12-valuent 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 christmasmiraclemaker across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for christmasmiraclemaker (version 1.0.0).

Part of a larger attack: 2023-12-valuent published 17 malicious packages. See the full campaign →

Malicious package

christmasmiraclemakerPyPI

Advisory published Nov 30, 2024Updated Dec 12, 2025

christmasmiraclemaker is a confirmed malicious PyPI package (MAL-2024-12234) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in christmasmiraclemaker (PyPI)

MAL-2024-12234

Immediate action

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

pip uninstall christmasmiraclemaker

What this malware does

Packages either test the malicious behaviour, or actually download and run a simple remote script during the installation.

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: 2023-12-valuent

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.
Downloads and executes a remote malicious script.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

eaad450cf6849b7e69a69cc6baaad3bce6d384a1e0ea513796a86fcfbc19c45e

64f06a86dd5b916af92fc3adf5c1e5638df9eaa156a1bc122e4e647f2aae236e

a26fbacd340cc136f838c93e3690de1f7844b6c249944c4ac85b593afd1dc1e1

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for christmasmiraclemaker (version 1.0.0).
If you installed it — respond
christmasmiraclemaker 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 christmasmiraclemaker was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. christmasmiraclemaker on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2023-12-valuent

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database