Which versions of svcmanager are malicious?

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

How do I remediate svcmanager if I installed it?

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

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

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

Search your lockfiles and build artifacts for svcmanager (version 1.0.1).

Malicious package

svcmanagerPyPI

Advisory published Jul 18, 2025Updated Dec 12, 2025

svcmanager is a confirmed malicious PyPI package (MAL-2025-191883) 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 svcmanager (PyPI)

MAL-2025-191883

Immediate action

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

pip uninstall svcmanager

What this malware does

Package attempts to download an executable and install it as a privileged service. The executable seems to be modified remote access tool

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

Campaign: 2025-07-svcmanager

Reasons (based on the campaign):

Downloads and executes a remote executable.
backdoor

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

b246a2c68861b1549c61024d647675cde75bccc78bea5b1a1b2425cb0b4dae66

062d589e7c49394864a13694f3de2a89589fd2f5e6a4d2e43e35ce136b6e7e9c

5db033907a8de7edf2b6e79903d4552d0ac4d6943f4827c8a162313ab1c7a984

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for svcmanager (version 1.0.1).
If you installed it — respond
svcmanager 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 svcmanager 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. svcmanager 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

2025-07-svcmanager

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks svcmanager-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