A researcher rooted his own Samsung TV, then lost his OpenAI account

On 21 October a reverse engineer posting as @log4j announced a root shell on his own 2025 Samsung TV and what he called "PRIVACY HORROR" inside its Tizen firmware. Two days later he said OpenAI had deactivated his account for "Cyber Abuse." Neither company has explained either half in public.

What the teardown reports

Log4j says he started because the ads on the set were "weirdly targeted." The firmware was AES-encrypted, so he went in through UART and JTAG and got root. What he described, in posts rather than a write-up, was telemetry from packet logs, audio categorisation, screenshots and a cross-device advertising identifier, with vision models running on the set itself. He also reported a region-specific neural network tracking what gets watched and which ads get skipped. For sets with no microphone, he said the software hunts for a nearby device that has one.

The feature Samsung already advertises

Not all of it is secret. Samsung's own SmartThings page says the TV "can detect noises like barking through its microphone" and play the pet's favourite content. A Hacker News commenter noted Samsung "has been pitching" such features "for years." That does not settle the teardown. A microphone that classifies a bark is documented. Whether audio is retained, leaves the set, or is joined to an ad identifier is not. Samsung has not responded.

The ban and the missing explanation

The only public record of the ban is what log4j posted: a deactivation notice citing "Cyber Abuse." He says he never used OpenAI's tools to find vulnerabilities, only for local work on his own hardware, at a cost of roughly $500. In a reply he guessed a "primitive classifier" was responsible. OpenAI's own deactivation article lists five reason categories, and "Cyber Abuse" is not one of them; the nearest is "circumventing security or access restrictions." The company has not commented.

The Claude claim does not fit the timeline

On 25 October an r/LocalLLaMA post said Claude had blocked REA, spelled there as "Reserve Engineer Anything." REA is actually Reverse Engineer Anything, an MIT-licensed MCP server that hands binaries to an agent. Anthropic has published nothing about it; users describe a safety check firing mid-conversation, a refusal inside the product rather than a published policy. The dates are harder: the r/claude thread reporting that guardrail went up on 21 October at 17:36 UTC, before log4j mentioned a ban. Whatever shifted at Anthropic, this ban did not cause it.

Documented: a rooted television, a deactivation notice, users hitting a guardrail. Not documented: Samsung's answer, the name of the on-device model, whether audio ever leaves the set, or that Anthropic changed any policy. Earlier this month a developer used Ghidra and Claude Code to reverse-engineer LG's webOS stack for a Plex client, with no ban reported.