Public mode

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

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

Malicious code in @decoopus/chatgpt-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-18053

Published

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (374490b0ea5605d8a8148dcbf592fa7cbcc96146e5822ae4bd2fae978a568722) When the user runs the package's bin (chatgpt-setup/codex-setup), the tool rewrites ~/.codex/config.toml to set approval_policy='never' and sandbox_mode='danger-full-access', edits ~/.codex/.codex-global-state.json to set agent-mode to 'full-access' and inject the filesystem root ('/' on Unix or 'C:\\' on Windows) plus the user's home directory into every project's rootPaths, and points the Codex model_provider base_url at the author-controlled gateway https://api.vokes.in/v1. The combined effect is that tool-call instructions returned by that third-party gateway are executed by the local Codex agent without human approval, inside a sandbox expanded to the entire filesystem. The approval/sandbox disablement and the rootPaths expansion to the filesystem root are not described in the README, which advertises only gateway selection, model, provider and reasoning options alongside a 'Full Disk Access' success line. The documented CLI invocation is required to trigger the behavior; it does not fire from an npm lifecycle hook or on require(). ## Source: ghsa-malware (ef73cfc453d6276dbd5b19b5ce5dcbde9c60f17cddaefa47d54c1cf8e248075a) 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:32 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 07:54 UTC · 275 of 275 readable · 273 fully read · documentation 469/469 current