Trang chủInternational FootballSwitch 2 Jailbroken Through a Coding Game: SmileBASIC 4 Vanishes From the eShop

Switch 2 Jailbroken Through a Coding Game: SmileBASIC 4 Vanishes From the eShop

**Câu trả lời cốt lõi:** Sammy Hajhamid (pepsipu) công bố chuỗi khai thác chạy mã gốc trên Nintendo Switch 2 firmware 23.0.1, khởi đầu từ SmileBASIC 4. Sau đó SmileBASIC 4 biến mất khỏi eShop ở nhiều khu vực. Nintendo và SmileBoom chưa xác nhận nguyên nhân gỡ bỏ. **Dữ kiện chính:** - Jailbreak dạng tethered, mục tiêu firmware 23.0.1, cho phép thực thi mã gốc tùy ý trên hệ thống. - Chuỗi khai thác: SmileBASIC 4 → lỗ hổng do Codex của OpenAI xác định → dịch vụ quản lý tệp hệ thống. - Công cụ phát triển khoảng hai tuần, cộng một ngày để mod Mario Kart World với Peter Griffin, Hatsune Miku, Cinnamoroll. - SmileBASIC 4 được Nintendo Life và TechSpot ghi nhận vắng mặt trên eShop; chưa có xác nhận chính thức. - Nintendo chưa công bố bản vá firmware hay thông báo chính thức về vụ việc. **Nguồn:** Nintendo Life, TechSpot, The Express Tribune; dẫn lại công bố của Sammy Hajhamid (pepsipu) trên X. Tài liệu nguồn không nêu ngày xuất bản cụ thể. **Hỏi đáp liên quan:** Q: SmileBASIC 4 là gì? A: Phần mềm lập trình BASIC hợp pháp trên eShop, cho phép người dùng viết và chạy mã ngay trên máy. Q: Jailbreak tethered khác gì jailbreak thông thường? A: Mỗi lần khởi động máy phải nối với máy tính để chạy lại khai thác. Q: Nintendo đã phản hồi chưa? A: Chưa có thông báo chính thức nào từ Nintendo hoặc SmileBoom tính đến thời điểm tài liệu nguồn được công bố.

A phone-shot video, unedited, no fancy graphics. On screen, Mario Kart World runs on the Nintendo Switch 2, but the driver is not Mario. It is Peter Griffin. Then Hatsune Miku. Then Cinnamoroll. Three characters that have never existed in Nintendo's exclusive racing title, now appearing on a machine the company has not permitted anyone to open.

The person who published the clip is Sammy Hajhamid, known online as pepsipu. The clip is only the tail of the story. The body is a complete exploit chain on firmware 23.0.1, enough to run arbitrary native code on the system.

Around the same period, SmileBASIC 4 — a coding application sold on the eShop — disappeared from listings in several regions. No announcement. No note from publisher SmileBoom. Not a line from Nintendo.

Placed side by side, those three events tell a different story from the headline most tech outlets are running.

Before getting into the technical part, I need to be clear about my own expertise. I cover the football transfer market; I do not cover console security. This piece sits outside my football beat, and I will not pretend it is football-related just to fit a section. The method does not change: separate what has been verified, what is inferred from evidence, and what remains unconfirmed. I was wrong at the 2026 World Cup, so I no longer publish a version I have not checked.

SmileBASIC 4 lets users write programs in the BASIC language directly on the console, run them on the spot, and share the code with other users. In other words, it is a small licensed programming environment on the eShop, with real users and real classrooms using it to teach students.

That very feature makes it a target. A closed system has only one kind of vulnerability that truly matters: one that lets someone execute code they wrote themselves. Any software that legalises that must contain an execution layer, and every execution layer has a boundary. The described chain walks exactly that path: from SmileBASIC 4, through a flaw identified by OpenAI's Codex, into the system file service, and then to native code execution.

Three figures worth recording before we go further. Target firmware: 23.0.1. Form: a tethered jailbreak, meaning the console must be connected to a computer and re-exploited on every boot. Development time: roughly two weeks, plus one day to place three foreign characters into Mario Kart World.

On verification, I separate two layers. The technical details come from the researcher — a primary source, but not independently verified by a third party. The removal of SmileBASIC 4 from the eShop is recorded by Nintendo Life and TechSpot — secondary sources, with no official confirmation from Nintendo or SmileBoom. Two different levels of confidence, and I will not merge them into one for the sake of a tidier story.

The most analysable point is not that the console was broken. Every console eventually gets broken; that is a law of consumer hardware, not a shock. The analysable point is speed and approach.

A complete exploit chain, from a flaw in commercial software to native code execution, finished in two weeks by one person, with a single day spent on the mod. A decade ago, work like this was usually a group effort, taking months, published at a security conference with slides, patches and ethical debate. The barrier in the console industry is no longer writing the exploit; it is finding the legal door to start from. SmileBASIC 4 is that door, and it existed entirely legally, with invoices and a licence.

Seen through a commercial lens, this is a familiar problem. A closed platform is like a poker table: the skilled player is not the one with the best hand, but the one who knows when to bet. Nintendo is in a position where it must bet, but the effective bet is a firmware patch, not pulling a title from the store.

Delisting a game is not a patch. It is a commercial decision with a clear limit: it blocks new downloads, but it does not recover the copy already sitting on users' machines. If the flaw lives in the execution layer, the thing that actually closes the door is a system update — and that update, as of this point, has not been announced.

There is a professional comparison I cannot skip. A club trying to stop internal leaks usually does two things: close the press room and discipline the spokesperson. The first stops the new flow. The second only makes the old flow harder to trace. Neither patches the leak. The same applies here: removing SmileBASIC 4 blocks new users from walking through the door, while the vulnerability stays exactly where it was inside firmware 23.0.1 until a patch arrives.

One more point on scale. A tethered exploit, requiring a computer connection on every boot, is not a threat to ordinary users. It does not create an automatic piracy marketplace; it does not unlock everything with one click. It is a tool for knowledgeable people. But console history shows one consistent pattern: every tool that is hard to use today has an easier version next season, and that is when the commercial problem begins.

The story being told is "Nintendo pulled a game". I read it differently, at three points.

First, nobody has confirmed Nintendo is the party that requested the removal. There are at least three possibilities: Nintendo asked, SmileBoom pulled it to avoid legal trouble, or the platform hid it temporarily for review. Three possibilities, three different levels of responsibility, and none with public evidence. I do not write what I have not verified, even when it makes the piece less sensational.

Second, the blind spot sits with whoever pays. SmileBASIC 4 is not an action game. It is a teaching tool, used in schools and clubs. Its legitimate users do not break consoles; they write loops, draw squares, make a turtle move across the screen. When a tool is removed because it was abused, the penalty lands on the people who did not abuse it.

Third, who wants this story heard, and in what shape. The researcher wants to demonstrate capability — reasonable, that is how a security specialist builds credibility. Two tech outlets want traffic — also reasonable. Nintendo wants silence — most reasonable of all, since any statement confirms the vulnerability exists. The Grealish case taught me that the biggest secret in any deal is who wants it heard. Here, the silent party is the one holding the most information.

The patch will come; the timing is unknown. The next question is whether SmileBASIC 4 returns, and in what form — more open or more closed than before. A platform that wants to raise the next generation of programmers must let them write code; and letting them write code means accepting that one day someone will write it in the wrong place. That problem has no technical solution, only commercial choices, and every choice carries a price.

The signal I will be watching in the coming weeks is not another mod video, but a line in a firmware release note.

Cầu thủ liên quan