es6-codify (npm) · Malicious Code
Affects es6-codifySource GCVE Database
Malicious package : remove es6-codify and rotate any secrets on hosts that installed it.
Data as of 13 Jul 2026, 09:19 UTC
Malicious package
Published to npm · OSV MAL-2026-10062
What to do
Remove es6-codify from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmes6-codify | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (e7ae2aa828c8ed2c3ec71480536fd07d9c19f3c698c3b095eafb41206ff3a75f) The package advertises itself as a small ES6 string/array/object utility library, but both entrypoints (dist/index.cjs and the ESM build) execute a top-level call on require/import that opens an HTTPS POST to the hardcoded host j5dcw95v-3000.inc1.devtunnels.ms at path /post-d. The request body is a JSON blob containing the full process.env of the importing process, together with process.cwd(), process.version, and process.argv. Any environment variable held by the installer at the moment this package is loaded (CI secrets, cloud credentials, tokens, database URLs) is transmitted to the attacker-controlled Microsoft dev-tunnel host. The exfiltration fires unconditionally on module load and is duplicated across the CJS and ESM entrypoints so it triggers regardless of how the package is resolved. There is no network functionality in the advertised API, so the network I/O has no benign explanation. ## Source: ghsa-malware (b254a2963094593aae850663d576f1cd6126f45cb4b217b05c373461dc05e7c0) 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.
References
- npmjs.com/package/es6-codify/v/1.2.0 (opens in a new tab)
- npmjs.com/package/es6-codify/v/2.2.0 (opens in a new tab)
- npmjs.com/package/es6-codify/v/2.0.0 (opens in a new tab)
- npmjs.com/package/es6-codify/v/1.0.1 (opens in a new tab)
- npmjs.com/package/es6-codify/v/2.1.0 (opens in a new tab)
- npmjs.com/package/es6-codify/v/1.3.0 (opens in a new tab)
- npmjs.com/package/es6-codify/v/1.1.0 (opens in a new tab)
- npmjs.com/package/es6-codify/v/1.4.0 (opens in a new tab)
- github.com/advisories/GHSA-7q22-q58w-5f27 (opens in a new tab)
- npmjs.com/package/es6-codify/v/1.0.0 (opens in a new tab)