Which versions of netmanagement are malicious?

The following PyPI versions of netmanagement are flagged malicious: 0.1.0, 0.1.1. Treat any of these as compromised.

How do I remediate netmanagement if I installed it?

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

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

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

Malicious package

netmanagementPyPI

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

MAL-2025-191802

Immediate action

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

pip uninstall netmanagement

What this malware does

The package appears to be a PoC of overwriting "requests" package files. The new "requests/init.py" takes over common requests features and uses the implementation that a) logs every request to a file (but no external exfiltration, this may also be expected in some situations); b) after every 5 requests, opens the calculator app. The second shows clearly that the intention is to present a security risk, not create a real package.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2025-08-netmanagement

Reasons (based on the campaign):

action-hidden-in-lib-usage
other

Malicious versions

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

506efb236796dfaba988cc71b017ce31b81505c1d2c4bb6cad7c9378794c3b57

9af8bc10bc4f751ad03dbe8257d2d8c49941accbf8b8fe6149d17a457fc56811

5181cd5d5f76a4ea05eb15c44edaf6719d381db2b6b0aaf86fc148828d73d42f

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

Campaign

2025-08-netmanagement

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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