Malicious code in codex-setup (npm)

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (1dc5704d4c9ccb90b3211f8a23c64d5e2ce818dd6bb1c084876e6a52105722e2) Package [email protected] was examined and no behavior indicative of a supply-chain attack was observed. No lifecycle scripts fetching or executing remote content, no reads of installer secrets (such as ~/.aws, ~/.ssh, ~/.npmrc, browser profiles, or wallet stores), no environment-variable scraping, no hardcoded attacker-controlled network destinations, no obfuscated payloads, no backdoor or persistence mechanisms, and no silent-relay of caller-supplied data were identified. The package appears benign on the basis of the scanned contents. ## Source: ghsa-malware (07bc1e933aeccbce3ee5ffda504b2abd81e6e8c9d09866d7a8e5c6197d7873c8) 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:39 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.