Which versions of pathlib-v2-utility are malicious?

The following PyPI versions of pathlib-v2-utility are flagged malicious: 1.0.4, 1.0.5. Treat any of these as compromised.

How do I remediate pathlib-v2-utility if I installed it?

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

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

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

Malicious package

pathlib-v2-utilityPyPI

Malicious code in pathlib-v2-utility (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-697

Immediate action

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

pip uninstall pathlib-v2-utility

What this malware does

Disguised as file system manipulation library, the package hides an obfuscated code to communicate with a Telegram channel. Though the usage is not known at the moment, the package is clearly created for data exfiltration

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

Campaign: 2026-02-pathfiles

Reasons (based on the campaign):

obfuscation
action-hidden-in-lib-usage

Malicious versions

2 flagged

1.0.41.0.5

Indicators of compromise (SHA-256)

c8dc8b60e188fb941aeb9f5b6207d2c0fcab27719a142558498bf72d1602d992

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

Campaign

2026-02-pathfiles

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

O3 blocks pathlib-v2-utility-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