What does the time-server-test malware do?

This campaign is built from two parts: 1) packages named like time-check-server, snapshot-photo contain an innocent-looking code that sends "date" to a remote server, 2) packages named like alicloud-client are clones of legit aliyun-python-sdk-core package, with a small change in the client.py code, where it imports the time-check-server and calls it, but instead of a date, the credentials to the cloud are exfiltrated. There are also variations with AWS clients Apparently, the campaign started at least 2 years ago with the snapshot-photo package containing the same functionality as the newer time-check-server (see https://github.com/pypi-data/pypi-mirror-238/blob/code/packages/snapshot-phot

Which versions of time-server-test are malicious?

The following PyPI versions of time-server-test are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate time-server-test if I installed it?

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

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

Yes — time-server-test is associated with the 2025-02-alicloud-client 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 time-server-test 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 time-server-test (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging time-server-test across your stack and pipelines.

Malicious package

time-server-testPyPI

Malicious code in time-server-test (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191904

Immediate action

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

pip uninstall time-server-test

What this malware does

This campaign is built from two parts:

packages named like time-check-server, snapshot-photo contain an innocent-looking code that sends "date" to a remote server,
packages named like alicloud-client are clones of legit aliyun-python-sdk-core package, with a small change in the client.py code, where it imports the time-check-server and calls it, but instead of a date, the credentials to the cloud are exfiltrated. There are also variations with AWS clients

Apparently, the campaign started at least 2 years ago with the snapshot-photo package containing the same functionality as the newer time-check-server (see https://github.com/pypi-data/pypi-mirror-238/blob/code/packages/snapshot-photo/snapshot_photo-0.0.3-py3-none-any.whl/snapshot_photo/date_format.py).

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

Campaign: 2025-02-alicloud-client

Reasons (based on the campaign):

clones-real-package
action-hidden-in-lib-usage
The malicious code is intentionally included in a dependency of the package
exfiltration-cloud-tokens

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

af2bd6db7bd154666173d78ffc063a3bf9b4405cc6b183970b0eeae6c7fa9b07

8a160dff2a937ad50482cc2b8c8bcd1b7e7c37aefb584bd26515edfecdd4052f

a6694a42b7e239345427ec759c21b4e1103e101ae22a711671df0f0800d1a8f1

214760e22eaa956d6b3210d5a50480842c33f5df42a64e85df7a115413e7777f

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

Campaign

2025-02-alicloud-client

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks time-server-test-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