The Person Who Got Suspended From Codex While Poking at a Smart TV
You turn on the smart TV sitting in the middle of your living room, and a sponsored ad covering the whole screen pops up first. Pretty annoying.
And when ads that match your tastes and daily habits a little too well start showing up back to back, you get an uneasy feeling. So lately, a trend of tearing into the code inside home appliances with AI coding tools has really taken off.
These days AI is so good at 'reverse engineering' that even ordinary people can pick apart and modify simple programs.
Reverse engineering is the technique of analyzing hardware or software to work backward to its original design, structure, and operating principles. Think of it like tasting a finished dish and working backward to guess which ingredients and cooking methods were used.
Then, in late October 2026, a security researcher who was poking around a 2025 Samsung smart TV got blindsided. Active on X as @log4j, the researcher was digging into why this TV in particular showed such 'finely tailored ads.'
Then they got a notice from OpenAI that their account was suspended for a 'Cyber Abuse' violation, and they posted that email publicly.
They complained that the suspension cost them about $500, plus the usage-reset benefit they'd built up, and the debate spread in no time. Attempts to wipe ads off smart TVs were already happening all over the place.
✦ Gathin's Xiaomi Smart TV Ad Removal
X user Gathin
Just days before @log4j's Codex account was blocked, X user Gathin got rid of the ads that played before Netflix launched on the Xiaomi smart TV at Gathin's parents' home.
Gathin gave Anthropic's AI coding tool Claude Code the TV's model name, and Claude modified the smart TV, deleting 25 unnecessary manufacturer packages among other things, to build a launch screen with no ads.
Gathin shared it on the web, and it passed 6 million views. Beyond that, there was reviving a dead Lululemon smart workout mirror by loading new software on it, modding an old digital photo frame, and so on...
The boom in modding smart gadgets just kept rolling.
The Face of Reverse Engineering: REA
At the center of this boom is the open-source project Reverse Engineer Anything (REA), which took off this past October.
Built by developer morluto, this project is a connector tool that helps AI agents analyze programs with no source code, or the software inside devices.
As late as the end of September, it had only 34 stars on GitHub, but word of mouth added hundreds of thousands over October alone, and as of November 14 it had shot up to around 460,000. That's more than a 10,000-fold jump in a month and a half.
✦ REA's GitHub Stars
September 30 to November 14, 2026, count
A finished app or a TV's operating system goes into the device in binary, a language only computers can read.
Digging into that backward to uncover the internal structure is reverse engineering, and within it, the technique of analyzing machine code and rebuilding it as code in a higher-level language people can read is decompilation.
In the past, doing this meant firing up professional tools like Ghidra, a free tool released by the United States National Security Agency (NSA), IDA Pro, or Hopper, and an experienced engineer would sit on it for weeks or months.
✦ Here's How REA Connects Things
From an everyday question to the analysis result
But now we've got AI agents, right? REA links AI coding agents like Claude Code or Codex to professional tools like Ghidra, IDA Pro, and Hopper through the Model Context Protocol (MCP). That means a user can ask the AI agent in everyday natural language.
The AI uses the professional analysis tools to dig into the code, find the chunks of code related to the user's question, then collect all sorts of information, like what basis it used for its interpretation and what the evidence is, and report back.
Thanks to that, even ordinary users without deep security knowledge can easily see how the software in an electronic device is put together.
Isn't Reverse Engineering Basically Hacking?
But in November, the mood flipped fast. On user requests, the AIs that had been smoothly running reverse engineering started putting up a wall called 'security safeguards'.
A thread titled "The Dream is dead" went up on Reddit's r/ClaudeCode board, and complaints kept coming in on the REA Discord that Claude Code was refusing every decompilation request on 'safety check' grounds.
✦ From @log4j's Account Suspension to Restoration
October to November 2026
Back to the @log4j case from earlier: it came with a backstory and a correction.
As @log4j explained, they'd originally tried to dig into the Samsung TV's encrypted firmware, hit a wall, found a zero-day vulnerability on their own to get admin rights on the Tizen operating system, and used AI tools as a helper for the reverse engineering along the way.
So it wasn't just firmware poking after all.
On top of that, in an October 26 follow-up post, @log4j said the suspension probably had nothing to do with 'reverse engineering the Samsung TV.'
They corrected themselves, saying the safety classifier seemed to have malfunctioned from repeatedly seeing ordinary security and tech terms.
OpenAI engineer Tarun Gogineni (X account roon) said in a public reply the same day that there's no rule banning reverse engineering with Codex, and that most blocks were mistakes made in murky judgment territory.
Eleven days after the suspension, on November 3, OpenAI admitted the error, apologized, and restored @log4j's account.
Either way, it's true that OpenAI explained there's no rule against reverse engineering with Codex. But users' unease isn't going away, and there's a clear technical reason for that.
Reversing machine code, picking apart network packets, and finding hidden features inside a device: if you look at the actions alone, they look exactly like hacking.
Whether it's the hands analyzing firmware to strip ads from my own TV or the hands of a hacker hunting for security holes in some company's or home's devices... to an AI model, those will look like the same command.
Is the person sending the request the real owner of the product? Will they use that code for defense and repair, or for attack? Realistically, it's impossible for a cloud AI's automatic filter to sort that out perfectly every time.
Matt Brown, a principal consultant at Brown Fine Security, who was interviewed by 404 Media, said something similar.
Brown said they'd been blocked while running reverse engineering on cloud AI, and the blocks lined up almost 100% with the 'cyber' category, which covers hacking-like activity.
Dodging Cloud AI Blocks: People Moving to Local AI on Their Own Computers
✦ Why decomp.dev Closed New Submissions
October 15, 2026
As AI-powered reverse engineering took off, confusion hit the reverse engineering communities that had been active for years. A notable example: on October 15, decomp.dev, a collaboration site for decompiling classic games, closed new project submissions.
AI sped up decompilation work so much that unauthorized forks, rushed PC ports churned out in bulk, and leaderboard number races kept piling up, and decomp.dev concluded that the community's collaborative foundation had collapsed.
The developer who made decomp.wtf, an AI decompilation helper, also halted development on their own, saying they respect the pushback from the existing reverse engineering community.
But demand for AI reverse engineering hasn't gone away. So people who want to keep doing AI reverse engineering are walking away from cloud AI, where you never know when a policy change will block reverse engineering, and moving to open-weight local AI models.
Matt Brown, for one, switched to an open-weight model too, in place of cloud models whose security guardrails change without notice.
Brown shared a case on X where they used GLM-5.3-Flash, a model whose weights China's Z.ai (formerly Zhipu AI) released, to find the hidden Bluetooth commands of an IoT sensor on a propane tank themselves.
Even @log4j, who got suspended, said that from October 27 they'd started an eight-month experiment of cutting off cloud dependence and handling work only on local computing equipment.
If someone runs reverse engineering with a local LLM and modifies the programs in various smart devices without the manufacturer's agreement, is that okay? And if it is, where do we draw the line between that and hacking?
I have a feeling a lot of legally complicated issues will come up from here on.
That's all for this post. See you next time.
Codex Asks 'Want Some French Fries?' Prompt Adware Haiou
ChatGPT Lawsuit: "Cut Your Dose, Hide It From Your Doctor"
200-Page AI Complaints Are Burying UK Council Officials
🌐 Korean version: AI 리버스 엔지니어링으로 삼성 스마트TV의 광고를 없애려다가... Codex 계정을 차단당했다?
🌐 Japanese version: AIでサムスンTVの広告を消そうとして、Codexのアカウント停止?
No comments:
No comments yet. Want to leave the first one?
Post a Comment