Malicious code in chatgpt-desktop-setup (npm)
Published Sources: OSV (Schadpakete)
- Malicious package
What is affected, what to do
Uninstall the package, isolate affected environments and rotate credentials that were available during installation.
Not sure whether and how you are affected? Ask a question about this vulnerability
Malicious package
npmchatgpt-desktop-setup
“chatgpt-desktop-setup” is registered as malicious in the npm repository. Anyone who installed the package should uninstall it immediately, isolate affected environments and rotate credentials that were present during installation.
Affected versions (4)
- 1.0.0
- 1.0.1
- 1.0.2
- 1.0.3
purl: pkg:npm/chatgpt-desktop-setup
Sources (5)
ghsa-malware
GHSA-pgq5-xq28-533msha256: 7551b6bc0def507896edf6f75d5fe99a46d27eedbe55f69861c500b3c07551aa
amazon-inspector
IN-MAL-2026-021901Versions from this source: 1.0.2
sha256: 5c475553921237fa1c0ad5df34610023b93a7c00d13203981c43b883532bd072
amazon-inspector
IN-MAL-2026-021998Versions from this source: 1.0.3
sha256: a1da0b8da785dae09b76c5edc52b33d152dc130c9224abb2849fd234d8489166
amazon-inspector
IN-MAL-2026-022127Versions from this source: 1.0.1
sha256: af7e5220f485bc6f28fae5a77e125a9b491d861378af487846c88b422adced27
amazon-inspector
IN-MAL-2026-022128Versions from this source: 1.0.0
sha256: d9cdacb4686e25ec7261ce91a961645e8d79cb67dbfd67df12390ec056d3e1c7
The OSSF `malicious-packages` namespace lists packages flagged as malicious by static analysis or sandbox detonation. An entry here is a confirmed finding, not a suspicion.
Metrics
—
Priority
No value is available for this vulnerability.
—
CVSS v3
No value is available for this vulnerability.
—
EPSS score
No value is available for this vulnerability.
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 30.00 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
-= 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.