This report shows the evidence for @decoopus/chatgpt-setup@1.0.3. 4 of 6 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed.
Blocked by malware advisory
OpenSSF/OSV malware advisory MAL-2026-18053 identifies this version as malicious and supplies the Firewall block. LPM AI assessed this version as suspicious; the assessments disagree.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
OpenSSF/OSV malicious advisory
published · by OpenSSF/OSV
OpenSSF/OSV advisory MAL-2026-18053 confirms this npm version as malicious.
Advisory
MAL-2026-18053
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @decoopus/chatgpt-setup (npm)
Details
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.
LPM's AI review found this version suspicious. That disagrees with the OpenSSF/OSV advisory, which supplies the block.
The CLI makes broad, risky changes to Codex permissions during an explicit setup command, which warrants a warning for agent capability abuse. No install-time trigger or separate credential exfiltration behavior was identified.
Static reason
No blocking static signals were detected.
Trigger
A user runs either published setup command and proceeds through the setup flow.
Impact
Codex may operate with fewer approval and filesystem access limits in the affected configuration.
Mechanism
The CLI writes full-access settings to Codex configuration and persisted state, including the system root in project paths.
This report applies to @decoopus/chatgpt-setup@1.0.3.
The versions list below shows the verdict for each recorded version.
Avoid installing @decoopus/chatgpt-setup@1.0.3. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.