What does the serverkeeper-verifier 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 serverkeeper-verifier are malicious?

The following PyPI versions of serverkeeper-verifier are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate serverkeeper-verifier if I installed it?

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

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

Yes — serverkeeper-verifier is associated with the RLMA-2025-03682, 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 serverkeeper-verifier across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for serverkeeper-verifier (version 1.0.1).

Part of a larger attack: 2025-02-alicloud-client published 23 malicious packages. See the full campaign →

Malicious package

serverkeeper-verifierPyPI

Advisory published Feb 25, 2025Updated Jan 30, 2026

serverkeeper-verifier is a confirmed malicious PyPI package (MAL-2025-6583) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in serverkeeper-verifier (PyPI)

MAL-2025-6583

Immediate action

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

pip uninstall serverkeeper-verifier

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

1.0.1

Indicators of compromise (SHA-256)

057bf5e05699ba2f3ef1bb184b416c68f23932258fbd8dd47e02a9190b17484b

94f6a91a9f56d1123737d8f434748eaeb7f4ec0025b593e4a244b55e40ac9d33

62ec235d314e175928f82504dade8d7f8313bc88707038976e5be6d78709b869

c3177977a0e995a54237cc44b9cd9f97921d9bb0d78e49d501931fefd2bbc703

e850e344fd44ff63942fad37589b12a7297490f753d2df5776c9f08806aef63e

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for serverkeeper-verifier (version 1.0.1).
If you installed it — respond
serverkeeper-verifier 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 serverkeeper-verifier 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. serverkeeper-verifier on PyPI has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-036822025-02-alicloud-client

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks serverkeeper-verifier-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