Which versions of my-service-manager are malicious?

The following PyPI versions of my-service-manager are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7. Treat any of these as compromised.

How do I remediate my-service-manager if I installed it?

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

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

Yes — my-service-manager is associated with the 2024-12-BetterMint 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 my-service-manager across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for my-service-manager (8 malicious versions).

Malicious package

my-service-managerPyPI

Advisory published Dec 1, 2024Updated Dec 31, 2025

my-service-manager is a confirmed malicious PyPI package (MAL-2024-12309) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in my-service-manager (PyPI)

MAL-2024-12309

Immediate action

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

pip uninstall my-service-manager

What this malware does

While the package appears to be a manager for Windows service, the linked executable is an infostealer with capabilities like cookie stealing ang keylogger. The package only supports installing it

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

Campaign: 2024-12-BetterMint

Reasons (based on the campaign):

infostealer
exfiltration-generic
Downloads and executes a remote executable.
keylogger
exfiltration-browser-data
The package contains code to detect if it is running in a sandbox environment.

Malicious versions

8 flagged

1.0.01.0.11.0.21.0.31.0.41.0.51.0.61.0.7

Indicators of compromise (SHA-256)

4a778eb8adf461bb8148ebb35218c7eeab48140845a8552270f5551103a7a8fe

58c8e4c726cef11c6d7d60916210f532060a6ff7a98bb7fea5872eb10335dd5d

b309512854b18904781da57ddf4d172db809260ec141d96f4cff6ff3b1c4fc0e

be7d265b3561d43e84a1b0584266904da5a72d356e3fad0605b7b9e8e2e7e2d0

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for my-service-manager (8 malicious versions).
If you installed it — respond
my-service-manager 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 my-service-manager 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. my-service-manager on PyPI has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2024-12-BetterMint

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks my-service-manager-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