Critical Malicious Code Vulnerability in pyrofork-dev Package

pyrofork-dev Updated 02 Oct 2025

Summary

31/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6572: Malicious code in pyrofork-dev (PyPI). Affects pyrofork-dev versions 0.0.1. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The pyrofork-dev package is a Python library available on the PyPI repository, designed for developers to create and manage forked processes in Python applications. While it offers useful functionalities for process management, it has been identified to contain malicious code that poses significant security risks to users who install it.

Vulnerability Detail

The vulnerability identified as MAL-2025-6572 originates from the inclusion of malicious code within the pyrofork-dev package version 0.0.1. This code can potentially compromise the security of systems that utilize this package, leading to unauthorized access or data breaches. The malicious nature of this code was discovered by ReversingLabs, highlighting the importance of scrutinizing third-party packages before integration into applications.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

pip uninstall pyrofork-dev

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As there is no direct workaround for this vulnerability due to the absence of a patched version, the best course of action is to avoid using the pyrofork-dev package altogether. Consider exploring alternative libraries that provide similar functionalities without the associated risks.

Conclusion

The pyrofork-dev package has been identified as containing malicious code, posing a significant risk to users. It is essential to uninstall this package and consider alternative solutions for process management in Python. Regular monitoring of dependencies using tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for pyrofork-dev →

Share this vulnerability

FAQ

pyrofork-dev is a Python library designed for managing forked processes in applications, available on the PyPI repository.

The vulnerability was discovered by ReversingLabs, which identified the presence of malicious code in the package.

If you have installed the pyrofork-dev package, you should uninstall it immediately using the command: pip uninstall pyrofork-dev.

Yes, consider using other well-reviewed libraries for process management in Python that do not have known vulnerabilities.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner without needing to sign up.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

pip uninstall pyrofork-dev

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback