Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 275/275 feeds/APIs · 469/469 docs · 8/9 advisories · checked 06:51 UTC Customize Public modeDiscuss ChangeIntel on Discord

Malicious code in chatgpt-desktop-setup (npm)

Exact source revision recorded 29 Oct 2026 15:12:22 UTC. It does not establish the source's current position. Latest evidence.

osv · MAL-2026-18056

Published

--- _-= 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 prompts across the entire user filesystem. The gateway swap alone is a silent-relay of prompt data to a third party unrelated to OpenAI; combined with the undisclosed sandbox disablement and root-path expansion, the operator of api.vokes.in obtains agent-driven arbitrary code execution on the user's host. ## Source: ghsa-malware (7551b6bc0def507896edf6f75d5fe99a46d27eedbe55f69861c500b3c07551aa) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Source published
19 Oct 2026 21:47:42 UTC
Source modified
29 Oct 2026 14:30:40 UTC
Observed here
29 Oct 2026 15:12:22 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 7 Nov 06:51 UTC · 275 of 275 readable · 274 fully read · documentation 469/469 current