Unrated

symfont/process typosquatting malware spoofs symfony/process

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Packagist symfont/process
Affected
every version
Fixed in
no fixed version recorded

Sources

GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-g3j5-mpp2-2fqm lists affected ranges: Packagist symfont/process >=0
VerifiedObserved 26 Oct 2026, 13:56 UTCStructured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation

Exploitation: No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS: not scored
EPSS: No dated EPSS signal available.

Source description

As published by the source; long descriptions are shortened.

In September 2021, security researchers discovered a malicious Composer package called symfont/process, a typosquat targeting users of symfony/process. The malicious package has since been removed from Packagist.

Dates and revisions

Published by the source: 26 Jan 2023, 19:53 UTC
Last modified by the source: 26 Jan 2023, 19:53 UTC
Source last checked: 26 Oct 2026, 13:56 UTC

Revision 1 · created · 26 Oct 2026
Published from ghsa record GHSA-g3j5-mpp2-2fqm

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-g3j5-mpp2-2fqm

Advisory: symfont/process typosquatting malware spoofs symfony/process
IDs: GHSA-g3j5-mpp2-2fqm
Record: https://patchnext.com/advisories/ghsa-g3j5-mpp2-2fqm (revision 1, source checked 26 Oct 2026, 13:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist symfont/process: affected every version

## Suggested inspection (read-only)
- Packagist symfont/process: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on symfont/process.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-g3j5-mpp2-2fqm (GitHub-reviewed advisory GHSA-g3j5-mpp2-2fqm lists affected ranges: Packagist symfont/process >=0)

Commands are suggestions: review each one before running it.

Loading voting…