Which versions of calctestchristmas are malicious?

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

How do I remediate calctestchristmas if I installed it?

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

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

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

Malicious package

calctestchristmasPyPI

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

MAL-2024-12228

Immediate action

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

pip uninstall calctestchristmas

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)

66e3df409984415be2af4f91cfa37b270c55238d00fd70e5fe6e662ce410def6

cc3d0aad00732ac597c39a82c41efa9ec9a102544ff1540266321e31b1fdd3b5

2ca28313dde83e6a781be8018c9a9b55d5ae15f6341f79a412e199edf3d1e433

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