Which versions of cfgmgr-sync are malicious?

The following PyPI versions of cfgmgr-sync 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, 1.0.8, 1.0.9. Treat any of these as compromised.

How do I remediate cfgmgr-sync if I installed it?

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

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

Yes — cfgmgr-sync is associated with the 2026-03-cfgmgr-syn 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 cfgmgr-sync 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 cfgmgr-sync (10 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cfgmgr-sync across your stack and pipelines.

Malicious package

cfgmgr-syncPyPI

Malicious code in cfgmgr-sync (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-2000

Immediate action

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

pip uninstall cfgmgr-sync

What this malware does

The code exfiltrates content copied to clipboard content to a hardcoded location. The code is obfuscated and has a persistence mechanism.

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

Campaign: 2026-03-cfgmgr-syn

Reasons (based on the campaign):

clipboard-stealing
obfuscation
exfiltration-generic
persistence

Malicious versions

10 flagged

1.0.01.0.11.0.21.0.31.0.41.0.51.0.61.0.71.0.81.0.9

Indicators of compromise (SHA-256)

e3f72f18351a20c172ef8154055917c9e977fe782b32a4716faed582d67f3071

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 cfgmgr-sync (10 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cfgmgr-sync across your stack and pipelines.
If you installed it — respond
cfgmgr-sync 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 cfgmgr-sync 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 cfgmgr-sync 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. cfgmgr-sync 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, and 2 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-03-cfgmgr-syn

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

O3 blocks cfgmgr-sync-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