News for hackers. Stuff that matters.
Re:Do not install Zod 4.6.6 – might be infected by colinmcd on Monday October 12, 2026 @11:11AM (#50057591)
Zod maintainer here. As others have noted, no malware was shipped in any release. This was three weeks ago, and it was caught very quickly. All my git and npm credentials were immediately revoked to prevent further access. There's a security writeup from the NPM team here. [0]

It seems like a git push credential, probably an SSH key, was exfiltrated from my local computer. The attacker used this to try to push malicious versions of Zod, standard-schema, and nub. The release workflows for Zod and standard schema were already hardened against this (environment-scoped trusted publishing, which requires an npm credential), and they could not be triggered via simple commits. Nub's release CI was triggered but npm flagged the malware before it went out.

All my packages have been switched over to staged trusted publishing, which requires 2FA for any release. Since I don't know exactly what else what compromised I've also done a full OS re-install and rotated all creds present on the old machine at the time of the compromise.

Ironically this likely happened due to some work on a sandbox for Nub's package manager. The attack is consistent with a primitive older variant of a Shai-Hulud-style worm. While working on the sandbox, an ersatz agent likely executed a compromised version of some package on npm in a test run. I had safeguards against this (filtering out any OSV-flagged packages, etc) but perhaps there's an undiscovered malicious package. Future work on this work will happen on an isolated VM.

It seemed shady to scrub the commits from history, and it still isn't clear to me that doing so is better from a security standpoint. But since there are concerns around git bisect, etc, I've done so anyway. v4.6.6 will lose provenance, v4.6.7 is being released.

[0] https://github.com/orgs/community/discussions/208477

There are no comments on this comment yet.