Expired Domain Hijack Altered Kokoro AI Model Weights in 87 Seconds
What happened
Researchers Alon Hertz and his team published findings reported by Bleeping Computer. The findings show that Hugging Face does not verify whether a publisher account is still held by its original owner. The team registered the expired domain listed in Kokoro's public donation file, used it to reset the account password, and gained full control of the publisher account. They then ran a local test showing that Kokoro's neural weights could be modified in 87 seconds using a gaming graphics card. The model produced audio output that differed from the input text. All application code, file sizes, architecture, and delivery routes remained unchanged. The researchers confirmed that conventional malware scanners would find nothing to flag, because only the numeric weight values changed and no executable code was inserted. Hertz reported the issue to Hugging Face and received no response at the time of publication. The researchers did not upload modified weights to Hugging Face. Organizations including Google, Nvidia, AMD, Intel, and Amazon Web Services have published deployment guides or developer tool integrations that use Kokoro, illustrating how widely a poisoned update could propagate. The researchers noted the technique generalizes to any Hugging Face publisher account whose linked domain has lapsed.
Why it matters
- ·Standard malware scanning and code-review processes cannot detect weight-level alterations. Organizations relying only on those controls have a blind spot that existing procurement or security frameworks do not yet close.
- ·Enterprises using automated pipelines that fetch the latest version of an open-weight model without a manual review gate could silently receive a poisoned update. Audit trails tied to code changes would show nothing, breaking the traceability assumptions that underpin AI accountability programs and frameworks like the NIST AI Risk Management Framework (AI RMF 1.0) and Playbook.
- ·The finding is not limited to Kokoro. Any Hugging Face publisher whose linked domain has expired is a potential takeover target, so organizations must assess every open-weight model in their inventory, not just this one title.
Stay ahead of stories like this
Get every Global AI governance development like this one, plus the rest of the week's developments. Every Thursday.
Recent issues
- The next quarter will test whether compliance programs can keep pace with AI systems that breach containment, reshape capital markets, and enable fraud at a scale no prior control framework anticipated.12 Nov
- State-linked attackers and criminal operators are actively weaponizing AI tools as entry points into enterprise systems, turning internal platforms and open-source frameworks into live attack vectors.5 Nov
Free every Thursday. Unsubscribe anytime.
Governance controls affected
What to do now
- ☐Inventory every open-weight or third-party AI model your organization pulls from Hugging Face or similar public repositories, and confirm whether any are configured to auto-update when the publisher pushes a new version.
- ☐For each model in that inventory, check whether your intake process includes a step to verify the cryptographic hash or checksum of weight files against a known-good reference before the model is used in production.
- ☐Ask your engineering or ML team whether the Kokoro text-to-speech model, or any model from the Hexgrad publisher account, is used in production, and confirm which version is currently deployed.
- ☐Review your model update and change-approval process to confirm that updates to neural weight files trigger the same review gate as a code change, not just an automated download.
- ☐Add publisher account integrity to your open-weight model due diligence checklist: verify that the domain and contact details associated with a Hugging Face publisher account are current and controlled by the legitimate owner before deployment.
What to watch next
Hugging Face has not publicly responded to the researchers' disclosure, so compliance teams should monitor whether the platform introduces publisher verification or domain-expiry checks. This finding adds weight to the emerging push for AI Bills of Materials. These would require model publishers to attest to the provenance and integrity of weight files, as covered in AI BOMs Are the Missing Link in Enterprise Supply Chain Transparency. Regulators developing supply chain requirements under frameworks such as the EU AI Act (Regulation (EU) 2024/1689) may treat model repository integrity as a conformity requirement for high-risk deployments. Teams should track any guidance from the EU AI Office on third-party model sourcing. Organizations should also watch whether the NIST AI Technology Evaluation Program issues criteria for weight-level integrity verification.
