Security enthusiast reverse engineers their own Samsung TV, then ChatGPT account gets banned; Claude also restricts the reverse-engineering tool REA

Foreign guy "abuses" his own TV, gets his OpenAI account banned after 42 hours! Claude also cracks down hard Xinzhiyuan October 26, 2026 10:22:44 From Beijing

Breaking!

A man got his OpenAI account directly banned just for cracking his own purchased TV!

All he did was research and crack his own smart TV on his own computer.

But OpenAI judged his actions as "Cyber Abuse" and directly banned his account. Reportedly, this ban cost him $500.

Even more absurdly, Claude has also started putting the brakes on "reverse engineering everything."

Just today, Claude was revealed to have banned overnight the wildly popular reverse-engineering tool REA, topping trending searches and sparking heated discussion across the internet.

Many people found that when they ask Claude to take apart software, it suddenly slams on the brakes halfway through writing, and even rephrasing doesn't help.

On the same day, Anthropic and OpenAI came down hard on "reverse engineering everything."

Taking apart his own TV

His ChatGPT account was gone first

The protagonist of this internet-shaking incident is a security enthusiast, @log4j.

A few days ago, @log4j noticed that the ads pushed to his 2025 Samsung TV were eerily precise. So he decided to take matters into his own hands and crack it open to see.

It turned out this wasn't so simple.

Samsung had encrypted the entire TV firmware with AES; without the key, ordinary reverse-engineering methods all failed against this wall.

The developer ultimately had to use a "zero-day vulnerability" to pry open root access and burrow into the machine's underlying system.

When @log4j actually got inside, he saw things ordinary users would never see in their lifetime.

Always-on voice, dog-bark recognition, 400 parties sharing the spoils

alwaysonvoice.

Even without shouting "Hi Bixby," it stays on, always listening. Going deeper into the system, @log4j dug out a complete surveillance pipeline, each item of which alone is enough to send chills down your spine:

ACR (Automatic Content Recognition): what show you're watching, what ad, what image—it compares frame by frame and records it all.

Geolocation: where the person's home is, down to the precise location.

Network mapping: which devices are connected at home—phones, computers, smart speakers, cameras—it draws a map of your entire home network.

A complete telemetry data pipeline: every time you power on, change channels, adjust volume, how long you stay—all packaged and uploaded.

Four independent DRM systems: reinforced layer by layer to ensure this data business runs smoothly.

He even found a piece of code that can distinguish dog barks from baby cries and count each separately.

This TV doesn't just want to know what you're watching; it also wants to know whether you have a dog, whether you have kids, and how many times the child cried.

Put together, this information forms a family portrait precise enough to be terrifying.

And where does all this data ultimately flow? To Samsung itself, and to more than 400 partners.

A TV priced at $3,000 has become a 24/7 data collection terminal. And behind it is a massive business with over 400 parties sharing the spoils.

As soon as the post went out, it went viral instantly, with 1.3 million people flooding in to watch.

The first thing countless people did in the comments was the same action—get up in the middle of the night and unplug the TV's network cable.

At first glance, netizens seem to be making a fuss over nothing, but this is by no means groundless or baseless.

In December 2025, the Texas Attorney General filed lawsuits against Sony, Samsung, LG, Hisense, and TCL over ACR data collection (screenshots roughly every 500ms, etc.).

According to research from Northeastern University, 82% of households in the US own smart TVs, and these TVs may be quietly recording your every move.

They found over 57 million ACR (Automatic Content Recognition) detection records from other users' TVs, and anyone could read them directly without logging in.

And the real problem this research reveals is:

You may simply be unable to tell whether the privacy switch you turned off actually took effect.

And the problems with smart TVs go beyond privacy—everyone has suffered from smart TVs for a long time!

More than surveillance: smart TVs are no longer "TVs"

Recently, many developers have started sharing their own TV modification solutions:

Their goal is simple: to turn increasingly bloated smart TVs back into clean TVs that only play content.

For example, one afternoon, developer Gathin T. saw the overwhelming ads on his parents' TV screen and simply couldn't stand it anymore, so he decided to clean it up.

But this time, he didn't write code from scratch himself; he went straight for Claude Code.

Later, he recalled:

I had Claude Code connect to the TV via Wi-Fi, clean out all that junk, and then make a simple home screen keeping only the apps my parents would actually use.

Then I put the prompt on GitHub and posted before-and-after comparisons of the TV modification on X.

As a result, in just two days, thousands of people followed this method to modify their own TVs. Xiaomi, TCL, Sony, Fire TV, LG, and even one or two projectors.

Currently, the project has over 30,000 stars and more than 400 contributors on GitHub.

Some users found that simply telling Claude "help me crack the TV" got no cooperation from the AI at all—they needed more specific, more complex prompts before it would proceed.

And now, more trouble has arrived!

The truly surreal plot is only just beginning.

42 hours later, the ban hammer falls

Just 42 hours after @log4j's post went viral, OpenAI made its move.

An email informed him that his ChatGPT account was directly banned for "Cyber Abuse." @log4j said outright that he had lost about $500 in one go.

Furious, he publicly protested:

I never used OpenAI to hunt for vulnerabilities, to attack anyone, or to carry out any kind of cyber sabotage. I was just locally reverse-engineering my own home TV.

Logically airtight, but the ban hammer was not withdrawn.

And at almost the same moment OpenAI banned him, Claude on the other side quietly made its move too.

Claude strikes too

Just a few days ago, on Reddit, a developer posted about his experience:

He asked Claude to help write a reverse-engineering workbook. Claude was writing along fine at first, then halfway through it suddenly stopped and told him that "a safety check had halted its response."

He tried rephrasing the question, but Claude still refused to continue.

Right after that, another developer, Irushi, posted describing an almost identical scenario: using Opus 5.5 together with REA for reverse-engineering research, Claude analyzed things coherently at first, but as it wrote, the safety guardrails suddenly triggered and it flatly refused to write any further.

And with that, the plot comes full circle.

The two giants—one banning people, the other banning tools—have completed a tacit encirclement of the "reverse-engineer everything" trend.

The viral tool REA storms to No. 1 on GitHub

What exactly is REA, the tool that exposed Samsung TVs in public and put both OpenAI and Anthropic on high alert?

REA stands for Reverse Engineer Anything—literally "reverse-engineer everything."

The name is bold enough, and its strength lives up to that boldness.

At its core, it is an MCP server plus a command-line tool, open-sourced under the most permissive MIT license. Look at this timeline to get a sense of how fast it took off:

April 14: the project was quietly open-sourced on GitHub; October 8: it shot to No. 1 on the GitHub trending list; October 19: its star count surpassed 330,000.

An open-source tool racking up hundreds of thousands of stars in less than a month after launch—what does that even mean?

At the time, developers across the internet were spreading the word: "another OpenClaw-level marvel has appeared."

Why is it so popular? Because it turns something that used to have an extremely high barrier to entry into a one-sentence affair.

Traditional reverse engineering is nothing short of a "craft." You first have to pick tools—Ghidra, IDA, Hopper—then learn each of their interfaces, manually move evidence from one program to another; finally you have to rely on experience to judge where to look next.

What REA does is package this entire complex workflow and hand it to an AI agent to run.

After installing it with a single command, npx rea-agents setup, mainstream coding agents like Claude Code, Codex, Cursor, and Gemini CLI can invoke it with one click.

All you have to do next is say one plain-language sentence: "help me figure out how this feature is implemented."

The rest is left to the AI. It will dispatch Ghidra, IDA, or Hopper on its own, automatically obtain pseudocode, assembly instructions, strings, symbol tables, and function call relationships, and like a detective following the clues, trace all the way down to the lowest-level code logic behind the feature.

The things it can take apart are astonishingly numerous, covering almost every form in the software world.

Native binaries, JavaScript and Electron apps, .NET assemblies, Android APKs and devices, websites and packet capture records, and even firmware, WASM, and SQLite databases.

Even more rare is its "evidence system." REA strictly divides every conclusion into three tiers: directly observed, logically inferred, and speculative.

It never packages guesses as facts; when the data is incomplete, it honestly tells you "this part is incomplete."

It is precisely this ability to "expose everything with one sentence" that sends chills down the spines of the big companies.

"Abusing the TV"—who exactly is the abuser?

But in this drama, who is the victim?

A TV that eavesdrops on you every day, profiles your home network, can count how many times your child cried, and then sells all of it to 400 companies—is it the victim?

Someone who spent $3,000 to buy it and merely wanted to see clearly what it was doing behind his back—does he become the abuser instead?

The roles have been completely inverted.

When you try to resist, try to see the truth, OpenAI turns around and tells you with a righteous face: you are abusing it.

That is the most jarring part. The TV seems to have been endowed with some kind of inviolable dignity.

This has long since gone beyond the technical question of whether reverse engineering is compliant. This is an ethical question—and one whose answer the manufacturers quietly made for us.

What the big companies truly fear is that reverse engineering itself has suddenly lost its barrier to entry.

In the past, those who could pry open commercial black boxes were a tiny handful of top security experts—limited in number and high in cost, something the big companies could still handle. But now, tools like REA have handed a key that opens every door to every ordinary developer.

Once everyone has a hammer, even the most intricate black box will sooner or later be cracked open. Today it's a Samsung TV; tomorrow it might be some app's paywall.

Next time the ban button is pressed, who will it be protecting?

Editors: Taozi, David