Berlin engineer Yannick Dixken found about 23 bugs in his Prusa MK4S, then proved the worst one by putting Rick Astley on its screen. Prusa patched them all in firmware 7.0.0.
Most people who get Rickrolled click a bad link. Yannick Dixken’s 3D printer got Rickrolled over the network.
Dixken, a Berlin-based freelance platform engineer, spent a week in August poking at his own Prusa MK4S. He came away with “14 findings, roughly 23 individual defects,” he wrote in a blog post titled “Never gonna print you up!”
The worst of them ended with “the printer’s main controller running code I sent it over the network.” His proof was a frame from Rick Astley’s famous music video, sitting on the printer’s screen.
Prusa has fixed every one of the bugs. Tom’s Hardware picked up the story on Tuesday, Nov. 10.
Watch the Clownfish TV podcast on YouTube. Article continues below.
How did a 3D printer get Rickrolled?
The prank sat on top of a real security hole. Dixken’s demo showed a still from “Never Gonna Give You Up” laid over the firmware’s error dialog on the MK4S display.
“Hey Rick, what are you doing on my printer?!” reads his caption for the photo.
The flaw behind it is what security people call remote code execution. In plain terms, someone else’s code could run on the printer’s main board. “Yup, fully fledged RCE,” Dixken wrote.
That bug scored 8.1 out of 10 on the standard severity scale, which counts as high. It involved Prusa Connect, the company’s cloud and self-hosted tool for managing printers remotely, according to Tom’s Hardware.
What other bugs did he find?
Plenty. Dixken’s list includes memory bugs, a problem with how the printer handled USB file names and crashes caused by malformed encrypted print files.
He also found a way to tie up the printer’s network connection, plus an encrypted download path with no integrity check. Two more of his findings scored above 7, and most landed in the medium range.
Some bugs were reproduced on real hardware, while others were confirmed only in the source code. His write-up labels which is which.
Tom’s Hardware said many of the bugs were probably symptoms of how the original developers used assert statements. Those are checks that are supposed to catch impossible situations in code.
Did he use AI to find the Prusa bugs?
Yes. Dixken wrote that he worked “armed with Opus 4.8 and a fuzzer.” Opus 4.8 is a version of Anthropic’s Claude AI model. A fuzzer is a tool that throws junk data at software to see what breaks.
He said the AI handled much of the grunt work, such as checking results and ruling out dead ends. He kept himself in “the driver’s seat,” in his words.
It wasn’t smooth. Dixken wrote that the model repeatedly gave up on the remote code path and insisted it couldn’t be done. He pushed back with his own review and steered it back on course.
He also admitted some of his AI-assisted write-ups came out messy, so he cleaned them up before sending them. Elsewhere in the post, he criticized low-quality AI bug reports that pile work on open-source volunteers.
Is my Prusa printer safe?
If it’s updated, yes. The fixes are in Prusa’s Buddy firmware 7.0.0 and later, and Dixken listed 15 affected models. They include the MK4S, MK4, MK3.5, MINI, XL and the CORE One family.
Prusa’s MK4S changelog lists “Improved security and robustness” for version 7.0.0, released Oct. 15. Makers101 reported that Prusa emailed owners on Oct. 30 asking them to update “as soon as possible.”
Dixken also noted the most serious bug requires an attacker to control or intercept the printer’s cloud connection. According to his post, Prusa says it knows of no real-world attacks, “except for my printer, which got rick-rolled.”
He plans to release his full proof-of-concept code later, after owners have had time to patch. So if your printer is still on version 6, now’s the time.
How did Prusa respond?
By most accounts, well. Dixken first posted his video online half-jokingly, asking if the printer was supposed to do that. A Prusa community manager reached out within minutes, he wrote.
Prusa reproduced the bugs on its own hardware, asked him to wait until the fix was out and credited his work, and he got a reward. He published on Monday, Nov. 2, alongside Prusa’s own advisories.
Dixken contrasted that with another disclosure that drew a letter from a law firm. “Only one of those two responses makes the next researcher pick up the phone,” he wrote.
The printer is patched, the bugs are public and Rick Astley has one more unlikely stage on his resume.
Article compiled and written by Thom Pratt (editor-in-chief), Derek Gibbs (beat editor) and the Clownfish TV newsroom.
D/REZZED is part of Clownfish TV. For more news, views, and rants on gaming, tech, and pop culture, subscribe at clownfishtv.com. Watch the show on YouTube at @ClownfishTV where new episodes drop daily. Subscribe to the Clownfish TV podcast on Apple Podcasts, Spotify, iHeart, and wherever else you get your podcasts.
Hat Tips:
-
Yannick Dixken, his blog (Nov. 2): The findings, the AI workflow, Prusa’s response and the quotes.
-
Tom’s Hardware, Mark Tyson (Nov. 10): The Rickroll, the 8.1 score and the assert detail.
-
Prusa Research, MK4S changelog: The 7.0.0 security fix and release date.
-
Makers101 (Oct. 31): Prusa’s update email.
AI Disclosure: All articles are assigned, edited and reviewed by an experienced human editor before posting. Like most modern newsrooms, WebReef Media uses a variety of AI tools to help with accuracy and efficiency. Ways AI may be used in article creation include research, grammar, fact-checking and ideation, as well as occasional AI generated or enhanced thumbnails or graphics. No articles are generated or posted without human oversight or involvement.


