This documentary brilliantly illustrates the "Weakest Link Principle" by showing how a single overlooked vulnerability can compromise an entire security ecosystem. It serves as a stark reminder that a system's strength is defined not by its most robust defenses, but by its most obscure flaw.
Install our extension to search inside any video instantly.
One QR Code Destroyed The 3DS ForeverAdded:
The year is 2014.
A teenager in suburban Ohio is standing in line at a GameStop at 7:00 in the morning.
He is holding $40 in crumpled bills. He skipped first period to be here.
He is here for a video game that 2 weeks ago was sitting in a clearance bin [music] marked $5 for 2.
A game that critics universally agreed was one of the worst titles ever released on the Nintendo 3DS.
A game about a square ninja named CC who could only move when you physically tilted the entire console, ruining the only feature the 3DS was actually known for. The game is called Cubic Ninja.
The teenager is not here because he wants to play Cubic [music] Ninja.
Nobody in the entire history of the medium has ever wanted to play Cubic Ninja.
He is here because somewhere in the broken, unresponsive, gyroscope-controlled code of this commercial disaster, [music] a 22-year-old French hacker named Jordan Rabet had discovered a single mathematical error, a digital box 1 in too small.
And through that 1 in, the entire Nintendo 3DS, a console Nintendo had spent 3 years and millions of dollars engineering to be the most secure piece of consumer hardware in the world, was about to fall apart. This is the story of how a square ninja killed the fortress. The year is 2007.
The original Nintendo DS is the best-selling handheld console on the planet. It will eventually move over 150 million units.
It is also, by any honest accounting, the single most pirated piece of consumer hardware in human history. The reason for this is a small black cartridge called the R4.
The R4 looks exactly like a real DS game. Slots into the console. It boots up. but inside the plastic shell is a microSD card slot. And on that card, a pirate can store every Nintendo DS game ever released, downloaded for free from the open internet. The R4 costs $15.
It works on every DS ever sold. Nintendo has no software update mechanism powerful enough to stop it. They cannot patch it. They cannot block it. They cannot recall it.
For the better part of a decade, Nintendo of Japan watches in slow, grinding horror as their flagship platform becomes the most lucrative piracy delivery system the industry has ever seen. Internal estimates of lost software revenue run into the hundreds of millions of dollars.
Children, [music] the most valuable demographic Nintendo has ever cultivated, learn before they can drive a car that video games are something you download for free.
When Nintendo's hardware engineers sit down in 2009 to draft the next handheld console, the mandate from corporate is not subtle.
It is not negotiable. It is absolute.
The next console must be unhackable. Not difficult to hack. [music] Not expensive to hack. Unhackable.
Mathematically, cryptographically, architecturally unhackable.
>> [music] >> What they design over the next 2 years is, by the standards of 2011, a masterpiece of paranoid engineering.
>> [music] >> The Nintendo 3DS ships with not one, but two processors.
The main processor, an ARM11, runs the games and the user interface. This is the part of the system the user can see.
The second processor, an ARM9, is hidden. The user will never know it exists.
The ARM9 has one job, and it does it with the cold focus of a prison guard.
[music] It controls every cryptographic operation on the entire device.
It is the only chip allowed to talk to the AES encryption hardware.
It is the only chip allowed to read or write the system's internal storage.
It is the only chip that holds the keys to the kingdom.
The two processors cannot read each other's memory.
They cannot read each other's code.
They live in physically separate regions of silicon.
Separated by walls Nintendo's engineers [music] built specifically so that if the front-facing processor is ever compromised, >> [music] >> the attacker is still on the wrong side of the moat.
To request anything sensitive, the ARM 11 must send a formal monitored message across a narrow communication channel called PXI.
Like a prisoner slipping the note under a steel door, [music] the ARM 9 reads the note. If it approves, it returns the answer.
The ARM 11 never touches the keys.
On top of this physical separation, Nintendo layers cryptography.
Every piece of firmware on the device is signed with RSA 2048, a mathematical signature >> [music] >> that requires Nintendo's secret private key to forge. Every boot sequence is verified by an immutable boot ROM.
Code that is literally burned into the silicon [music] at the factory and cannot be changed by any software update ever for the entire life of the console.
The encryption engine has 64 hardware key slots, designed so that once a key is written into a slot, the key itself can never be read back out. [music] You can use it, you can never see it.
By every cybersecurity metric available in 2011, the Nintendo 3DS is a fortress.
To break it, an attacker would have to find a flaw in a game, escape the game sandbox, >> [music] >> escape the operating system sandbox, hijack the message channel between processors. [music] Bridge the air gap to the ARM9 and somehow defeat hardware level encryption.
The architecture is not just secure, it is showy.
It is the kind of security that engineers show off at conferences.
For 3 years it works.
Flash card manufacturers try, they fail.
>> [music] >> The few hacks that exist are fragile, patchable, and require soldering. The 3DS, the console that was supposed to never be another [music] R4 disaster, sits on store shelves untouched.
And then a 19-year-old French university [music] student notices a level editor in a $5 puzzle game. Jordan Rabet, online handle Smealum, is not a pirate.
This is important.
Smealum has said it on the record, >> [music] >> in interviews, in forum posts, in conference talks, more times than anyone can count. [music] He does not pirate games.
He does not believe in piracy.
He thinks pirating games hurts the developers who make them.
>> [music] >> And he refuses to release any tool whose primary purpose is to enable theft.
[music] What Smealum believes in is something older and stranger and harder to corporate PR away.
Smealum believes that when you buy a piece of hardware, the hardware belongs to you, not in some abstract legal sense.
In the actual sense. The plastic, the silicon, the circuitry, yours.
And if you want to write your own programs and run them on your own machine, no corporation on Earth has the moral right to stop you. This belief has a name.
It is called the homebrew ethos.
It is the same belief that built the Apple II, the same belief that built Linux, the same belief that in the early 2010s was being slowly, deliberately strangled by every major hardware [music] manufacturer on the planet. Smealum wants to run Minecraft on his 3DS.
[music] He has, in fact, already written a version. He calls it 3DS Craft.
He wants to write emulators [music] so that people can preserve classic Nintendo games that Nintendo itself has stopped selling. He wants to bypass the absurd regional locks that prevent an American 3DS from playing a Japanese game.
He wants to make the machine he bought do what he wants it to do. [music] And to do any of this, he needs a way in.
For 2 years, he hunts.
He reads disassembled Nintendo code in the dark hours of the morning. He talks to a small network of collaborators on encrypted channels.
Hackers operating under names like yellows8 and pluto and Derek. The slow accretion of a brain trust.
They look at every game on the system.
They look at every native application.
They look at the web browser, the camera app, the street pass [music] system, the system settings.
They are looking for one thing.
A single piece of software that takes input from the outside world, >> [music] >> processes that input, and trusts it. And then somebody notices Cubic Ninja.
[music] Cubic Ninja is a disaster. The reviews are merciless.
Metacritic [music] settles at 51. The controls are unplayable. The art is generic. The level design is sadistic.
Critics specifically hate on the developer for building a game around tilting the console when tilting [music] the console destroys the auto stereoscopic 3D effect that is the entire selling point of the hardware.
>> [music] >> The publisher, Ubisoft, releases it and immediately seems to forget about it.
The original developer, AQ Interactive, goes out of business.
The game sits in clearance bins. Nobody buys it. Nobody plays it. Nobody cares.
But Cubic Ninja has one feature. You can build your own custom puzzle stages >> [music] >> and share them with your friends.
And because this is 2011, and because the 3DS has a camera, [music] the sharing mechanism is a QR code. You design a level.
The game encodes it into a barcode.
Your friend points his camera at the barcode. The game decodes the data >> [music] >> and loads the level into memory.
When Smealum looks at the code that loads a Cubic Ninja QR code into memory, what he sees is the kind of mistake that haunts software engineers in their dreams.
The developers, sometime in 2010, had to decide how big a custom level could be.
They picked a number. They wrote that number into the source code.
They allocated a block of memory exactly that big to hold the [music] incoming level data when a QR code was scanned.
And then, in a single fateful oversight that would eventually cost Nintendo control of an entire console generation, they forgot to check.
The code never verifies that the incoming data is actually small enough to fit in the box. In computer security, this is called a stack buffer overflow.
It is the oldest, most thoroughly documented, most preventable category of software vulnerability in existence.
Universities teach freshmen how to find them.
There are automated tools that scan for them.
There are entire programming languages designed specifically to make them impossible.
And in 2010, inside the code of a $5 puzzle game about a tilting ninja, AQ Interactive shipped one to the entire global market. Smealum writes a QR code that contains, [music] instead of a level, a payload.
The payload is too big for the box.
When Cubic Ninja tries to load it, the excess data spills out of the buffer and overwrites the surrounding memory.
And because Smealum has calibrated the spillage with surgical precision, the bytes [music] that land on top of the program counter, the internal compass that tells the processor what to do next, are bytes that Smealum picked. The compass no longer points to the next puzzle tile.
It points to Smealum's code. This is the moment the fortress falls, but this is only the first wall.
The ARM 11 is breached, but Cubic Ninja is sandboxed. The exploit is sitting inside a tiny corner of the system with almost no permissions.
It cannot touch the SD card. It cannot install software.
It cannot do anything except run within the dying corpse of a tilting puzzle game. To actually do something useful, >> [music] >> Smealum needs to escape.
He looks at the GPU.
The 3DS's graphics processor, [music] like every modern graphics chip, has a feature called direct memory access. The GPU can read and write certain regions of system memory >> [music] >> without asking the CPU for permission.
This is a performance feature. It exists so that [music] the GPU can quickly grab textures and dump rendered frames without waiting in line.
It is not supposed to be a security [music] feature. Smealum realizes that some of the memory regions the GPU can [music] write are regions that the CPU sandbox would never let him touch.
[music] Specifically, the memory belonging to other applications, including the system's built-in web browser, which has dramatically [music] higher privileges than Cubic Ninja does.
So, Smealum, sitting inside the corpse of Cubic [music] Ninja, sends rendering commands to the GPU. He instructs the graphics chip to act as a contract killer. [music] The GPU, oblivious, executes the commands.
It writes Smealum's payload into the memory of the web browser.
>> [music] >> The web browser, now silently corrupted, executes the payload.
The browser connects to the internet, downloads a second stage installer from Smealum's server, and installs [music] a custom launcher onto the 3DS's home screen.
This launcher is called the homebrew launcher. It can [music] run any unsigned program a user wants to write or download.
The fortress is open. He calls the entire chain Ninjhax.
On November 17, 2014, Smealum publicly announces that Ninjhax is real, that it works on every 3DS sold to that date, and that the trigger is Cubic Ninja. He had originally planned to release it earlier, but Nintendo had announced a hardware revision called the New Nintendo 3DS, and Smealum [music] tactically delayed his release until the new model was actually in stores, ensuring [music] that Nintendo could not patch the vulnerability before launch.
The timing is brutal. The new hardware ships already broken.
The internet does what the internet does.
Within hours, [music] Cubic Ninja, a game that two days ago was sitting in clearance bins for $2, is being sold on eBay for $30, >> [music] >> then 40, then 60.
Within a week, GameStop's algorithm has marked up used copies to $40, while their own database, still functioning on the assumption that Cubic Ninja is shovelware, lists new copies at $20 [music] in the same store. Customers walk into GameStop's across America >> [music] >> and explain to confused clerks that yes, they would in fact like to pay twice as much for a used copy of a game that has unsold new copies sitting on the same shelf.
Some listings on Amazon reach $130.
Isolated panic auctions on eBay reportedly cross $500.
Collectors, hackers, and resellers strip the world's retail supply of Cubic Ninja in approximately 72 hours.
>> [music] >> Nintendo of Japan, witnessing this in real time, does the only thing they can do.
The game has a digital release on the Japanese eShop. They yank it.
Within days, [music] Cubic Ninja is delisted, scrubbed from the Japanese storefront, removed from existence as a downloadable product.
But in the rest of the world, where Cubic Ninja was only sold on physical cartridges, Nintendo can do nothing.
The original publisher is bankrupt. The cartridges are in attics and dorm rooms [music] and backpacks all over the world.
The weapon is already distributed, and here is where Nintendo discovers the worst part.
They cannot patch the cartridge. The Cubic Ninja exploit is not a flaw in the operating system.
It is a flaw in a game that Nintendo did not write, did not publish, and no longer controls. Every copy of Cubic Ninja that exists in the wild, on every 3DS forever, contains the original unpatched vulnerability.
Nintendo can patch the GPU bug. They can patch the browser bug. They can patch the chain.
They cannot patch the cartridge.
As long as the cartridge exists, a sufficiently determined attacker can find a way to use it.
What follows is 3 years of escalating war. Nintendo patches the GPU memory exploit.
The community responds with a new attack >> [music] >> that uses corrupted save files in The Legend of Zelda: Ocarina of Time.
Nintendo patches that. [music] The community releases an exploit using a forgotten eShop game called Freaky Forms Deluxe, Nintendo pulls Freaky Forms from the eShop. The community releases browser [music] hacks, an exploit in the built-in web browser triggered by visiting a single URL.
Nintendo patches the browser.
The community releases sound hacks, >> [music] >> an exploit that does not need internet, does not need a cartridge, does not need anything except a single specially encoded M4A audio file played in [music] the 3DS's native music app.
Nintendo cannot remove the music app.
They cannot remove the browser.
They cannot remove any of these features without crippling the device for legitimate [music] users. Every patch lags. Every patch is incomplete.
Every patch arrives weeks after the next exploit is already in circulation.
>> [music] >> And while Nintendo is busy plugging holes in the ARM11, smealum and his collaborators are no longer interested [music] in the ARM11.
They have set their sights on the ARM9.
In December 2015 at the Chaos Communication Congress security conference in Hamburg, [music] smealum, derrek, and plutoo walk onto a stage and present their [music] findings to a room of professional security researchers.
The talk is methodical.
It is the kind of talk that, if you understand what you are watching, makes the hair on the back of your neck stand [music] up. They explain that Nintendo's ARM9 firmware, the holy of holies of the entire console, the part of the system that was supposed to be physically and cryptographically untouchable, was encrypted using AES in electronic codebook mode, ECB, the cryptographic mode that every textbook in the world specifically warns you not to use because [music] it preserves patterns in the encrypted data.
They explain that Nintendo's firmware loader never bothered to verify whether the decryption key it was [music] using was actually the right key.
It just decrypted whatever it was given and ran the result.
This means that if an attacker writes garbage data into [music] the system's encryption key store, the firmware loader will dutifully decrypt the firmware into garbage [music] and try to execute it.
Most of the time, the garbage will be nonsense and the system will crash.
But by sheer mathematical chance, somewhere between 23 and 50% of the time, the garbage will resolve into a valid arm branch instruction and the processor will jump to wherever the branch points. If the attacker has carefully placed his own code at that destination ahead of time, the system will [music] execute it.
On the arm 9 with full privileges, before the operating system has even loaded. This exploit becomes known as arm [music] 9 loader hacks. It is no longer a buffer overflow.
It is no longer a clever trick.
It is permanent custom firmware that loads milliseconds after the power button is pressed, [music] beneath the operating system itself, with absolute control over both processors. Fortress is not breached.
>> [music] >> Fortress is occupied.
And then in 2017, the final blow.
A researcher named Derek begins analyzing the RSA 2048 signature verification in the boot ROM itself.
The boot ROM, the immutable code burned into the silicon, the part of the system that Nintendo specifically designed to be impossible to patch, even by the company that built it. He finds a flaw in how the boot ROM parses cryptographic signatures.
Specifically, in how it validates the PKCS standard padding around an RSA signature. The parser is sloppy.
The padding fields are not properly checked.
Derrick realizes that with a sufficiently creative forgery, he can construct an RSA signature that the boot ROM will accept as valid, even though it was never signed by Nintendo's private key. The math is [music] wrong. The signature is fake.
The boot ROM does not care, but there is one catch.
The forged signature has to be delivered through the system's hidden [music] factory recovery mode, which Nintendo designed for fixing bricked consoles on the assembly line.
The recovery mode can only be triggered if a specific button combination is held down [music] while a special DS cartridge is inserted into the slot. And critically, [music] the system has to believe it is closed.
On the clamshell 3DS models, this is a problem.
You cannot hold a button combination while the lid is shut.
The buttons are inside the closed shell where your fingers cannot reach.
The community solves this with a refrigerator magnet.
The 3DS detects whether the lid is closed using a small hall effect sensor that responds [music] to a magnet built into the screen housing.
If you place a household magnet against the bottom shell of the console, the sensor reports that the lid is closed even while it is open.
You hold the buttons. You insert the flash card. You boot the system. The boot ROM accepts the forged signature.
The custom firmware loads.
This exploit is called boot9strap.
>> [music] >> It exists in the part of the chip that is physically incapable of being patched. Nintendo cannot issue a software update to fix it. They cannot recall the consoles.
They cannot manufacture new units without redesigning the silicon.
Every 3DS ever made, including every 3DS that will ever be made until Nintendo retools the entire production line, is permanently and irrevocably broken. The console is dead. In the aftermath, Nintendo does the only thing left to do.
They start over.
The Nintendo Switch is designed from scratch on a completely new operating system called Horizon.
Horizon [music] is a microkernel. It is built on the assumption that every application will eventually be compromised.
It assumes the attacker is already inside. Even if a buffer overflow is [music] found in a Switch game tomorrow, the attacker is trapped inside a sandbox that has no path to anywhere important.
[music] No file system access. No SD card access. No path to the kernel. The lessons of the 3DS are etched into every line of code. smealum, in the years [music] after, transitions to professional security research.
He works on the Wii U. He works on the Switch. He works on iOS. He never sells an exploit to anyone. He never enables a piracy ring. He stays consistent with the only thing he ever said he believed in.
The hardware belongs [music] to whoever bought it.
Nintendo spent 3 years and millions of dollars building a fortress designed by some of the most paranoid hardware engineers in consumer [music] electronics.
They built two processors. They walled off memory.
They burned cryptography into the silicon. [music] They invented a security architecture so robust that the security community in 2011 considered the console mathematically impossible to compromise.
And they were undone in the end [music] because a Japanese studio that no longer exists, working on a $5 puzzle game that nobody bought, forgot to check the size of a digital box.
The teenager in Ohio, the one who skipped first period to stand in line at GameStop, walked out of the store that morning holding a copy of Cubic Ninja and a printed QR code from a French hacker's website. He went home. He pointed his console's camera at the barcode. The fortress fell open in his hands. Somewhere [music] in the silicon of every Nintendo 3DS ever sold, the ninja is still there.
The box is still too small. Compass is still waiting to be pointed somewhere else.
And as long as one cartridge survives >> [music] >> in one attic, on one shelf, in one closet, in one home, in one city in the world, the door cannot be closed again.
[music] Nintendo learned the hard way the oldest law in computer security.
It does not matter how thick the walls are.
It does not matter how clever the locks are.
It does not matter how much you spent on the gate.
The fortress is only as strong [music] as the dumbest piece of code that lives inside it.
And somewhere in every fortress ever built, >> [music] >> there is a forgotten room with a forgotten door.
And somebody, eventually, is going to walk through it.
Related Videos
Agentforce NOW AMA: Build with React and Salesforce Multi-Framework
SalesforceDevs
490 views•2026-05-28
How agent o11y differs from traditional o11y — Phil Hetzel, Braintrust
aiDotEngineer
450 views•2026-05-28
WEB TECHNOLOGIES UNIT-2 | Degree 4th sem BCOM Computers web technologies unit-2 full explanation💯✅
LearnwithSahera
1K views•2026-05-29
More tests are always better? How to use AI to identify tests that bring little value
Alliance4Qualification
335 views•2026-05-29
Search Algorithms Explained in 60 Seconds! 🤖💨
samarthtuliofficial
218 views•2026-06-01
People of Game of Thrones using JavaScript DOM
AltCampus
296 views•2026-05-30
Introduction to Problem Solving Part - 1 | Lecture 1 | Intermediate DSA
ascensionix
107 views•2026-05-29
So What's Odin Lang Even Good For
TechOverTea
131 views•2026-06-01
