One hundred and forty-four GitHub repositories disappeared this week, swapped for a single takedown page. The casualty was not an emulator but something smaller and, for Switch modders, far more essential: the firmware that powers modchips like Picofly, SX Core and HWFLY.
According to an IGN report, Nintendo filed four separate DMCA notices with GitHub on 6 November. Two targeted emulators — the Citron Neo project, whose own network of 71 repositories was disabled, and two standalone copies of Yuzu. But the firmware notice was the headline act, and TorrentFreak believes it marks the first time Nintendo has gone after modchip firmware on GitHub at all.
What the takedown notice alleges
The notice, published in GitHub’s public DMCA archive on 10 November, rests entirely on the console’s technological protection measures, or TPMs. Nintendo argues that the Switch only interacts with legitimate game files because its boot sequence and cryptographic signatures verify software before anything is allowed to run.
“The firmware allows Nintendo Switch modchips to illegally circumvent Nintendo’s TPMs in order to run illegal copies of Nintendo Switch games.”
GitHub’s record names a single parent repository, Ansem-SoD/Picofly. Yet because the network exceeded one hundred repositories and Nintendo asserted that all or most forks infringed to the same extent, GitHub disabled the entire 144-strong set in one pass — a blanket approach that has become familiar in the company’s anti-piracy strategy.
Why firmware is a harder blow than emulators
Early Switch consoles shipped with an unpatchable exploit in recovery mode. Later hardware — the Switch Lite and OLED models — closed that hole, which means running custom software on a patched console requires physical modification: soldering a Picofly, HWFLY or SX Core chip directly to the motherboard. The firmware is what those chips run, performing the voltage glitching during boot that cracks the console open.
That distinction matters. An emulator can be rewritten, renamed and re-uploaded within days, as the endless Yuzu forks proved. Firmware repositories are the reference material for hardware people already own, and losing them cuts off updates, reflashing and new installations at a stroke.
Key point: Consoles with a modchip already fitted keep working. The takedown blocks firmware updates and new installs — and the glitching hack never worked on Switch 2 in the first place.
It is also a blunt instrument. These chips enable homebrew applications, alternative operating systems such as Linux, game modding, custom themes and even overclocking. The notice draws no distinction between those uses and piracy, framing the firmware as a circumvention tool first and foremost.
The Team-Xecuter precedent
To shore up its anti-circumvention argument, Nintendo cited the US Department of Justice’s prosecution of Team-Xecuter, the group behind the SX Pro, SX Core and SX Lite chips. Member Gary Bowser was sentenced to forty months in prison in 2022, later released early for good behaviour. The criminal conviction gives Nintendo a comfortable legal foundation that emulator fights, which tend to settle quietly, never quite provided.
The company’s track record suggests it is only warming up. In 2024, a notice aimed at twelve Yuzu mirrors helped remove an estimated 8,500 copies of the emulator. In August this year, more than 400 Switch emulator repositories fell in a single day, with seven DMCA notices filed at once.
Some firmware is still out there
The sweep was not total. TorrentFreak spotted several Picofly and HWFLY firmware repositories still live on GitHub, one of which may even be the original Picofly source. Expect follow-up notices.
The timing adds spice. The notices landed just days after emulators managed to run the upcoming Ocarina of Time remake on PC, and emulation in 2026 is a different beast altogether — AI-built ports have proliferated so quickly that Anthropic coded a lock to stop Claude copying games outright, Rockstar took down a browser version of GTA 5, and Bethesda pulled an AI-generated Fallout New York project.
There is an irony in a company that has begun hiring for game preservation roles while simultaneously erasing the tools communities use to keep old hardware alive. Nintendo would argue the two are unrelated. Modders, unsurprisingly, see it differently.
With firmware mirrors still standing and a Switch 2 modding scene slowly taking shape, few in the community believe this sweep is the finish line. The question is not whether Nintendo will send more notices — it is how much of the Switch’s homebrew history survives the next one.

