Which versions of datetime-zones are malicious?

The following PyPI versions of datetime-zones are flagged malicious: 0.1.0, 0.2.0, 2.3.9. Treat any of these as compromised.

How do I remediate datetime-zones if I installed it?

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

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

Yes — datetime-zones is associated with the RLMA-2025-04757, 2025-09-datetime-zones, RLUA-2026-00249 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 datetime-zones 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 datetime-zones (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging datetime-zones across your stack and pipelines.

Malicious package

datetime-zonesPyPI

Malicious code in datetime-zones (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-47756

Immediate action

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

pip uninstall datetime-zones

What this malware does

During import, environment variables are exfiltrated

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

Campaign: 2025-09-datetime-zones

Reasons (based on the campaign):

exfiltration-env-variables

Malicious versions

3 flagged

0.1.00.2.02.3.9

Indicators of compromise (SHA-256)

88dbab1928062d862e8abfd5ab6669ead582a549643e94e31a67f643cd886ae8

ba264b5c0145300563416b657d95d26e4857ab607c180212c1b263b80e0f28fe

d1a3d123441a30b70e5c3317307e99636ac6d13c589e7fb1ae0253a6aaa96aaf

7bff7d04cf0481aa8f2e9e8f427d86b973a80ae2da58284f154a04cabf80c3e0

3e8849b6f34583e73407bc9d89fe09b6df211ab8cfffd3ac1d778b829ae24589

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

Campaign

RLMA-2025-047572025-09-datetime-zonesRLUA-2026-00249

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks datetime-zones-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