Source code of N64, GameCube, Wii & more: Massive Nintendo Leak

Google

Nintendo is currently experiencing massive leaks. In forums, the source codes for the operating systems of N64, Gamecube and Wii have appeared, as well as various unpublished builds to games on the net. The scale is not yet known.

A massive leak floods various Nintendo internals.

The headlines around Nintendo are more marked by glitches in recent days. Last week, we were able to report that Nintendo Account hacks had to confirm - the gateway was to an external service provider. As Nintendo Enthusiast is now advised, the company is also likely to face a massive data leak that makes countless content illegally available on the Internet.

The leak tells everything about the setup of the Nintendo Wii

Among other things, a detailed thread in the Resetera forum informs that there is now countless internal information about the N64, Gamecube and Wii in the net. In addition to the source code of the console operating systems, the Wii also counts so-called "Verilog files"." Verilog is a language used to describe hardware and is used to describe circuits by code," a forum user said. This makes it possible to follow up to the last detail how every single part of the Wii was manufactured.

Nintendo Wiinintendo Wii.

Despite the data now available, Nintendo Enthusiast does not expect the source codes of N64, Gamecube and Wii to provide great euphoria to developers of console emulators. For example, developers - like the popular Dolphin emulator - would deliberately keep away from leaks of this kind in order not to - even more - to get into very harsh legal waters.

intendo switch games.

But the potential that leaks have for enthusiasts who like to dig through code and spread sheets is still great. In particular, the leak will include around 2 terabytes of data. It is currently not known how the data was stolen from Nintendo, but initial evidence suggests that the external service provider Broadon may be part of the problem. Last but not least, there is speculation that the known hacker Zammis Clark, known as Wack0, may be responsible for the leak. For the time being, it is worth waiting to see what exactly is being revealed by the network community in the detailed investigation of the leaks and how exactly the leak has come about.