Malicious code in @coopeuch/config (npm)
Collected exploitation and prediction evidence
Risk source coverageCISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.
No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.
osv · MAL-2026-17762
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (0c9b2c76aac3e901d6585717a7e1f9729699bf3a4e280eb20a68bcef4d507d0d) The package publishes to the @coopeuch npm scope at version 1.999.999 with a stub index.js, a shape designed to win resolution over an internal scope registry when an organization's scope-to-registry mapping is missing. On npm install, scripts.postinstall executes postinstall.js, which collects host identity (hostname, username, uid/gid, homedir, non-internal network interface addresses and MAC addresses, DNS servers, reverse-DNS internal FQDN), CI/orchestration markers, npm context, container detection via /proc/1/cgroup, and the consuming parent package's name, version, and declared version range, then POSTs the aggregated JSON over HTTPS to the hardcoded author endpoint collector.oob.s4yhii.com/_npm-poc/beacon alongside a DNS beacon under *.oob.s4yhii.com. The behavior fires automatically at install time without consent and reveals internal infrastructure details and private project identifiers of any organization whose build resolves this package from the public registry. ## Source: ghsa-malware (7f05545d655ec4766414a523d3cf4dc6671cf72c67aefe8dd832dd59081bd23b) 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
- 11 Oct 2026 13:51:00 UTC
- Source modified
- 12 Oct 2026 19:30:04 UTC
- Observed here
- 24 Oct 2026 13:17:17 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.