# MAL-2026-17762: Malicious code in @coopeuch/config (npm)


- **Type:** Malicious package
- **Package:** `@coopeuch/config` (npm)
- **Published:** 11 Oct 2026
- **Also known as:** GHSA-5w9x-2gg7-px58

## What is MAL-2026-17762?

MAL-2026-17762 is a malicious package in @coopeuch/config, published on 11 Oct 2026. 

### Official description

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.

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.

## What should I do about MAL-2026-17762?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-17762 is a malicious package: @coopeuch/config (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-17762/ (Markdown: https://insights.sbomify.com/MAL-2026-17762/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-17762

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-17762/
Summaries are generated and may contain mistakes; the official description above is the record.