Which versions of mgrcfg are malicious?

The following PyPI versions of mgrcfg are flagged malicious: 1.6.7, 1.6.8, 1.6.9. Treat any of these as compromised.

How do I remediate mgrcfg if I installed it?

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

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

Yes — mgrcfg 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 mgrcfg 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 mgrcfg (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mgrcfg across your stack and pipelines.

Malicious package

mgrcfgPyPI

Malicious code in mgrcfg (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-2124

Immediate action

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

pip uninstall mgrcfg

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

3 flagged

1.6.71.6.81.6.9

Indicators of compromise (SHA-256)

eeb9b6975940ff31a6a0f6361fd93d8d361a3687103c94c011a6fdf510a2fdec

891f9583196c3190b727faac5c6dd0e65d3977208147947e25836f3b6fc527d5

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 mgrcfg (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mgrcfg across your stack and pipelines.
If you installed it — respond
mgrcfg 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 mgrcfg 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 mgrcfg 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. mgrcfg on PyPI has been identified as a malicious package (versions 1.6.7, 1.6.8, 1.6.9 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 mgrcfg-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