Which versions of pyrovider are malicious?

The following PyPI versions of pyrovider are flagged malicious: 10.0.1, 10.0.2, 10.0.3, 10.0.4, 10.0.5, 10.0.6. Treat any of these as compromised.

How do I remediate pyrovider if I installed it?

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

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

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

Malicious package

pyroviderPyPI

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

MAL-2025-191836

Immediate action

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

pip uninstall pyrovider

What this malware does

On importing the module, package exfiltrates basic data like username. It's obfuscated with a lot of meaningless text and has no other purpose

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-03-pyrovider

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

Malicious versions

6 flagged

10.0.110.0.210.0.310.0.410.0.510.0.6

Indicators of compromise (SHA-256)

bf04e1165bcc092863a197ba8653b5669eb3ca2de4214f3c15c5f33a2ad6058d

a346a7f634bedd557ab051ccf33b892a2b6420a97c426a877476b7a66b1acf55

8a284c8693df6b69a813c449df740a232856337eba2e3f6de000a030651f1364

19c9fdf0ca847c71135513283274654eff4dcaa62baf7fcd56919b9d031a198b

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

Campaign

2025-03-pyrovider

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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