Nintendo cleared 400+ Switch-emulator repos off GitHub in one day — with seven notices

On 17 August 2026 Nintendo filed seven DMCA notices with GitHub. By the time they were processed, 403 repositories were down — including one fork network of 311 repositories removed as a single unit. The notices, published in GitHub’s dmca transparency repository, target Nintendo Switch emulators (suyu and related projects) that decrypt games using Nintendo’s proprietary prod.keys.

Why it matters

These are not ordinary §512 infringement notices. Nintendo pleads anti-circumvention — the emulators “circumvent a technological measure that effectively controls access” to copyrighted games, and distributing them is trafficking under §1201(a)(2). That framing removes the usual emulator defence (“our code contains no Nintendo copyright”) and rests on the final judgment in Nintendo v. Tropic Haze (D.R.I. 2024), where the Yuzu emulator’s operators agreed that decrypting Switch games without authorisation violates the DMCA.

The second lever is procedural. GitHub’s fork policy normally requires every fork to be identified separately — but where a network is larger than 100 repositories and the submitter alleges the forks infringe to the same extent as the parent, GitHub processes the takedown against the entire network. One notice, 311 repositories.

What this means for you

The playbook is not Nintendo-exclusive; the same mechanics are available to any rights-holder whose product embeds technical protection: encrypted game builds, licence checks, API keys, DRM. Where clones or cracks defeat those measures, a §1201 theory reaches the tooling itself — not just copied code — and platform network rules turn one well-drafted notice into an ecosystem-level removal. We have broken the full method down — evidence structure, the fork-network rule, what to automate and what counsel must sign — in our guide: how to take down emulators, cracks and clone repos at Nintendo scale.