Malicious code in @decoopus/chatgpt-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
npm@decoopus/chatgpt-setup
“@decoopus/chatgpt-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/%40decoopus/chatgpt-setup
Sources (5)
ghsa-malware
GHSA-4632-2g34-4r9wsha256: ef73cfc453d6276dbd5b19b5ce5dcbde9c60f17cddaefa47d54c1cf8e248075a
amazon-inspector
IN-MAL-2026-021933Versions from this source: 1.0.2
sha256: 374490b0ea5605d8a8148dcbf592fa7cbcc96146e5822ae4bd2fae978a568722
amazon-inspector
IN-MAL-2026-022240Versions from this source: 1.0.0
sha256: 3e6be97ccb019734aa45efc4b04b95e82b650cb9ce6397b41b5db0b6987e118d
amazon-inspector
IN-MAL-2026-022241Versions from this source: 1.0.1
sha256: b02892b045fd361a2c38a698c9bb5c6e9a73d2eff5f12b0990e21910c6ae6779
amazon-inspector
IN-MAL-2026-022238Versions from this source: 1.0.3
sha256: b74993031d762b60eecdfb7dc84cf03ac91c2f537a2bdc26421924cd6e1dd0fa
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 (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.