Skip to content- Sources: primary, registry, discussion
- Summary: A commit attributed to the maintainer account added a file named
meta.test.mjs to both the zod and @zod/mini packages at version 4.6.6 and wired it to a preinstall hook, so it runs on plain npm install without the package being imported. The script reads an Ethereum contract through three public RPC endpoints, decodes a list of domains from the return value, fetches a /loader endpoint on each, writes a base64 payload to a temporary directory, and imports a second base64 stage as a data: URL, so the operator can repoint command and control through a chain write rather than through the package. The same commit changed the release workflow from maintainer-triggered dispatch to publishing on any version bump pushed to main, and the 4.6.6 publish carries an npm provenance attestation naming the GitHub Actions trusted publisher with approver colinhacks, which is the observable trace of that workflow change rather than a safety signal. The registry dates the 4.6.6 publish to 2026-10-11, and the version still resolves with full dist metadata and no deprecation marker, so it remains installable even though npm now lists 4.6.7 as the latest dist-tag. - Why it matters: zod is among the most depended on packages in the JavaScript ecosystem, so any install or CI run that resolved 4.6.6 should be treated as having executed untrusted code, with no import of the package required.
- Follow-up: Whether the commit is confirmed as an account compromise rather than maintainer action, which the diff alone cannot distinguish.