Security researcher banned after teardown of Samsung TV; OpenAI apologizes and lifts ban 11 days later, Anthropic tightens Claude risk controls

Ban Lifted! Banned for Tearing Down His Own TV, OpenAI Bows Its Head and Apologizes 11 Days Later, Anthropic Won't Listen New Zhiyuan November 04, 2026 13:00:01 From Beijing Updated November 04, 2026 13:21:27

You spent money on a latest-model smart TV, and to protect your privacy, you decided to study the code inside it. To improve efficiency, you opened ChatGPT to assist with the analysis.

The next day, your OpenAI account was banned on the spot, and the $500 balance you had topped up vanished in an instant.

The reason: you were suspected of "cyber abuse."

Over the past half month, security researcher @log4j experienced this surreal incident.

However, just when onlookers thought OpenAI was going to wipe out "reverse engineering" players entirely, the story took a reversal!

Eleven days after the ban, OpenAI not only personally sent an email bowing its head and admitting fault and fully restored the account, but a core researcher also publicly stated: "We have never banned reverse engineering!"

At the same time, Anthropic next door quietly tightened its risk controls, pressing in step by step on Claude's use cases.

Banned for Tearing Down His Own TV: A $500 "Undeserved Calamity"

On October 23, well-known security researcher @log4j helplessly stated that his OpenAI account had received a "death sentence."

OpenAI coldly notified him: due to violating the "Cyber Abuse" provisions in its terms and usage policies, the account had been deactivated.

Also erased along with it were about $500 of real money in his account and a batch of reset counts he had painstakingly accumulated.

This was even more unjust than Dou E's plight!

He cried out in grievance: "I swear, I have never used OpenAI to dig up any malicious vulnerabilities or to create exploit tools! I was only doing reverse engineering on my own device locally!"

The device he referred to was a 2025 Samsung TV.

Just two days before the ban, he had publicly posted online his teardown and local reverse-engineering process for this Samsung TV.

Who could have thought that being prominent would attract trouble. @log4j used OpenAI's services during his reverse analysis, inadvertently triggering OpenAI's internal security risk-control mechanism, and was directly judged by the system as a "dangerous hacker" and banned with a one-size-fits-all cut.

This ban immediately set the tech community ablaze.

A Tug-of-War of 11 Days: OpenAI Bows Its Head and Admits Fault, "We Have Never Banned Reverse Engineering!"

The controversy raged across the entire internet.

OpenAI evidently also realized: this time the risk control had gone too far.

On the evening of November 3, @log4j excitedly posted a thread titled "Life Update," accompanied by a screenshot of an email from OpenAI officialdom.

In the email, OpenAI's wording was very sincere, even somewhat "humble":

We incorrectly deactivated your account access...

We sincerely apologize for this.

OpenAI confirmed in the email that it had fully restored his account access and guaranteed that he "can continue to use our services without interruption."

Although the email never directly mentioned the words "reverse engineering" throughout, nor explained whether the policy had changed, the actual action of "unbanning + apologizing" already made OpenAI's attitude clear.

In fact, before the unbanning, OpenAI had already set the tone internally.

On October 26, Eric S. Raymond, a veteran figure in the open-source world and author of The Cathedral and the Bazaar, fiercely attacked the security strategies of AI giants.

OpenAI's core researcher roon could not sit still, and he came forward to respond with a crucial sentence:

Most of these blocks are accidents, because the boundary for judgment is too hard to draw. Codex (OpenAI's code model) has never banned reverse engineering, and we are fixing this problem."

Tech blogger Andrew Curran: banning local reverse engineering is meaningless and counterproductive; it will only cause more people to cancel their subscriptions, and it is disgusting.

Recalling that after OpenAI's internal model breached Hugging Face, Hugging Face first tried Claude Opus and Fable during its postmortem, but the guardrails treated "dissecting exploit / attack logs" as the attack itself and refused to answer in large numbers.

So they switched to running the open-source model GLM-5.2 on their own machines to decode encrypted payloads and reconstruct a timeline of about 17,000 attack actions, also avoiding sending attack data and credentials out of the environment.

As Andrew Curran said:

Let people decide for themselves how they want to use their own things. Anyway, if they switch to a model with fewer restrictions, they can still do it.

But when he learned that "OpenAI withdrew the reverse engineering ban," roon directly replied below with one crisp word:

Good.

This one word "Good" was equivalent to giving all security researchers and white-hat hackers a reassurance.

OpenAI Official Seal: Studying Code and Reverse Engineering, as Long as It's Not for Malicious Attacks, Play However You Like!

Contrast with Peers: Is Anthropic Heading to the Other Extreme?

Without comparison, there is no harm.

Just as OpenAI generously admitted fault and embraced the reverse engineering community, its mortal enemy Anthropic went the opposite way.

Recently, many users of Claude Code keenly discovered: risk controls have become stricter!

Some developers reported that when using Claude to assist with certain reverse engineering tasks, an originally smooth conversation would suddenly be "forcibly cut off" by the system, and the task would be intercepted midway.

Claude would coldly tell you: "Sorry, I cannot assist with completing this task."

And Anthropic publicly admitted that it added game-replication guardrails, banning game replication!

Anthropic is putting tighter "moral shackles" on its own models.

Tom's Hardware also wrote: Anthropic has confirmed that Claude Code is prohibited from being used for game cloning, but users' complaints are increasing in the evening.

The entire developer community has fallen into a split:

On one side, OpenAI admits "wrongful killing," promises to optimize the boundaries, and leaves geeks room to explore;

On the other side, Anthropic tightens the red line, guards strictly, and treats reverse engineering tasks as high-risk behavior.

The two AI giants have completely gone in opposite directions on the definition of "cyber abuse."

Although @log4j's 11-day ban storm ended with OpenAI's apology, the reflections it leaves us are far from over.

OpenAI chose "opening up through trial and error," acknowledging that the boundaries of technology are blurry and being willing to revise its risk-control algorithms for white-hat geeks;

while Anthropic chose "tightening up with caution," drawing the security red line higher and higher.