currentclockPyPI
Advisory published Updated
currentclock is a confirmed malicious PyPI package (MAL-2026-3206) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in currentclock (PyPI)
What this malware does
During import, the package automatically downloads and executes code that first acts as an infostealer and then starts code acting as a RAT. It connects with a hardcoded C2 server and waits for commands, supporting e.g. executing remote commands, exfiltrating files, recording the screen, executing GUI actions through PyAutoGUI.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-04-process-support
Reasons (based on the campaign):
-
exfiltration-generic
-
The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.
-
rat
-
spyware-like
-
infostealer
-
persistence
-
exfiltration-browser-data
-
exfiltration-crypto
-
files-exfiltration
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for currentclock (version 0.1.0).
If you installed it — respond
currentclock 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 currentclock 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
Campaign
References
Credits
- Kamil Mańkowski (kam193) · analyst
Detect & block this
O3 blocks currentclock-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.