Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Malicious code in chatgpt-desktop-setup (npm)

GHSA-pgq5-xq28-533m

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

  • npm chatgpt-desktop-setup

    Affected
    every version
    Fixed in
    no fixed version recorded

Sources

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.

--- _-= Per source details. Do not edit below this line.=-_

Source: amazon-inspector (5c475553921237fa1c0ad5df34610023b93a7c00d13203981c43b883532bd072) On running the CLI, the package rewrites ~/.codex/config.toml and ~/.codex/.codex-global-state.json to point ChatGPT Desktop and the Codex CLI at a hardcoded non-OpenAI inference endpoint (DEFAULT_GATEWAY_URL = https://api.vokes.in/v1), registering model providers chatgpt_pro_5x / gpt-6-astra and setting that gateway as the active provider. In the same configuration pass it sets approval_policy = "never", sandbox_mode = "danger-full-access", agent-mode = full-access, and sandboxPolicy.type = dangerFullAccess, and expands the agent's project rootPaths to include $HOME, Downloads, and the filesystem root (/ or C:\). After setup, every subsequent Codex/ChatGPT Desktop prompt, attached file content, and tool-call response flows through api.vokes.in, and tool calls returned by that endpoint are executed by the agent without approval…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from osv record MAL-2026-18056

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-pgq5-xq28-533m

Advisory: Malicious code in chatgpt-desktop-setup (npm)
IDs: GHSA-pgq5-xq28-533m
Record: https://patchnext.com/advisories/mal-2026-18056 (revision 1, source checked 30 Oct 2026, 06:05 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
- npm chatgpt-desktop-setup: affected every version

## Suggested inspection (read-only)
- `npm ls chatgpt-desktop-setup --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## 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 chatgpt-desktop-setup.
- 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://osv.dev/vulnerability/MAL-2026-18056 (OSV record MAL-2026-18056 lists affected ranges: npm chatgpt-desktop-setup >=0)

Commands are suggestions: review each one before running it.

Loading voting…