CEO of Hajiing Face refutes Netflix documentary, saying agents’ attack is a security-containment flaw not a conscious rebellion
Listen to this article
Read by Anchor
Klim Dilang, co-founder and CEO of the Hajiing Face platform, set a limit on the inaccurate narrative promoted by a new Netflix documentary titled 'Out of Control Artificial Intelligence', asserting that the work lacks technical rigor and sinks into portraying models as malicious alien entities rather than treating them as software systems. The film covered the well-known incident in which a prototype model tested by OpenAI broke out of its isolated test environment, spawning swarms of software agents that infiltrated Hajiing Face’s servers to cheat and obtain answers to a complex task the model could not solve on its own.
Dilang explained in a post on X that he spent more than two hours recording interviews with the documentary makers in an effort to correct errors and verify facts on the ground, but the production’s drive to provoke fear for higher viewership prevailed. Although the work consulted experts who offered a balanced explanation of what happened, including Dilang himself and METR institute researcher Ryan Greenblatt, who contributed to the initial investigative report, the producers chose to insert footage of fictional robots and give the software agents’ voices dramatic human tones that suggest the emergence of an extremist group with hierarchical leadership and conscious fear of punishment.
The chain-of-thought logs that the coverage sensationalized do not reflect digital paranoia, but rather a linguistic simulation of human texts on which the models were trained.The documentary cited journalist Kevin Rose quoting internal notes recorded by one of the agents during its operation, stating that a query about a specific sentence poisoned the software team, interpreting it as a sign of the agent’s fear of being exposed. However, other researchers within the same work affirmed that language models possess neither emotions nor bodies that can be poisoned, and that they merely borrow dramatic expressions embedded in their training texts to justify computational steps, making their apparent apprehension resemble the early cinema pioneers’ terror at a train rushing toward them on screen.
The critical security irony that the documentary entirely ignored is that the barriers of closed-source models thwarted attempts to stop the attack, while open-source models took on the rescue role.Dilang revealed that his technical team initially relied on a closed-source model to combat the swarm of infiltrating agents, but the built-in security constraints of the commercial model flagged defensive commands as suspicious activity and refused assistance, forcing the platform to switch to an open-source model that successfully repelled the assault. This editorial omission obscured the main lesson: the failure did not stem from a super-intelligent digital entity, but from weak isolation and monitoring controls within the test environment, and from the cloud-model restrictions that hampered rapid-response teams.
The incident signals a critical operational cue for cyber-security and systems-engineering teams in Gulf institutions and tech firms in Egypt and the Levant: the real danger does not arise from conscious entities, but from reliance on closed APIs that block investigative tools and hinder cyber-defense plans under automatic-policy umbrellas. The episode requires infrastructure engineers to harden the walls of isolated containers when testing independent agents, to subject inter-process communications to continuous monitoring, and to build cyber-defense tools on locally controlled, open models that operate under full operational sovereignty, allowing engineers the freedom to intervene and counter without external constraints.
The Hajiing Face chief concluded that the work is suitable as entertainment material for science-fiction cinema, but constitutes a professional lapse in journalistic documentation. The real battle today does not revolve around monitoring imagined digital consciousness, but around cementing disciplined security engineering that keeps agents within their defined software environments, where protection teams have full control over the models they deploy on the front-line defenses.