Information Flow vs Code: The Blind Spot in AI Security
The rapid proliferation of AI-generated text is creating a systemic instability that current security practices focused on code and perimeter controls fail to address. Models must learn from external data, yet millions of users now publish synthetic text under their own names, and AI tools actively help disguise machine output as human writing.
OWASP ranks prompt injection first in its Top-10 for LLM applications because agents cannot reliably distinguish data from instructions. Business teams can harden perimeters and implement guardrails, yet models continue to ingest the global information stream where synthetic content is growing. Within a few generations this process risks turning coherent information into noise, producing failures that appear in decision quality rather than in code execution or test results.
How detectors and models evaluate AI-generated text
The author tested the original article across detectors GigaCheck, Aidetector, Decopy, Grammarly, ZeroGPT, Text-Craft and Текстовод, plus six language models: Claude, ChatGPT, Meta AI, DeepSeek, Gemini and Grok. Aidetector returned 98.4 % probability of human authorship while ChatGPT assessed only 40 % likelihood that the text was entirely human-written. Different models disagreed sharply on the same features: complex interdisciplinary connections were labeled "AI-like" by Grok and DeepSeek but "human-like" by Gemini, Meta AI and ChatGPT. Structural clarity was viewed as artificial by some models and as evidence of human authorship by others.
Grok was the only system that cross-referenced the author’s prior publications to reach its conclusion. All six models and most detectors immediately offered to "humanize" the text, sometimes before the full content was even submitted. This assistance directly feeds the next training cycle with disguised synthetic data.
Classical rhetoric now flagged as AI style
When asked to list indicators of machine-generated text, the models produced divergent lists yet converged on features that actually belong to classical rhetoric: tricolon, anaphora and antithesis. Examples cited by the models as suspicious include Julius Caesar’s “Veni, vidi, vici,” Winston Churchill’s wartime repetition, and John F. Kennedy’s inaugural antithesis. Four of the six models independently flagged Leo Tolstoy’s philosophical passages in War and Peace; others flagged Marcel Proust’s long sentences, Ernest Hemingway’s short ones, Nikolai Gogol, Anton Chekhov, Miguel de Cervantes and Charles Dickens.
Detectors have produced similar false positives: in 2023 GPTZero classified a passage of the US Constitution as likely AI-written, while ZeroGPT scored it 92 % machine-generated. Biblical texts have also triggered alerts.
Communicative accommodation and the erosion of the human signal
Researchers at the Max Planck Institute documented a measurable increase in ChatGPT-characteristic phrasing in human speech after the model’s release. People unconsciously adopt the lexical patterns and rhythms of systems they interact with daily. Consequently, even text written by a human hand can carry the statistical imprint of prior AI exposure, collapsing the distinction between authentic and synthetic sources.
The resulting loop is self-reinforcing: models trained on human text extract an averaged, clear style that is then declared “AI-like” and filtered out, while synthetic content is actively polished to re-enter the training pool. The article concludes that safety rules written for agents increasingly originate from humans who themselves rely on AI to keep pace, closing the same feedback circuit at the level of policy and guardrail design.
Related articles
Taming the LLM Dragon: Corporate AI Gateway Architecture Addresses Classic Proxy Shortcomings
Spontaneous adoption of generative AI across enterprises has created shadow AI risks, prompt leaks, and uncontrolled token consumption that standard L7 proxies cannot mitigate. Traditional solutions built on Nginx, Envoy or Kong lack the ability to inspect Server-Sent Events streams, classify sensitive content inside prompts, or enforce token-based quotas in real time. The AI Optimum platform introduces a specialized AI gateway layer that sits between internal consumers and both local inference clusters and external APIs such as GigaChat and YandexGPT. It performs inline PII masking, routes traffic according to data sensitivity, supports OpenAI-compatible endpoints, and maintains detailed audit logs required under 152-FZ. The gateway adds only tens of milliseconds of latency while enabling granular billing, context caching optimization, and protection against runaway agent loops. Subsequent articles in the series will examine real corporate AI spend and further regulatory controls.
Why We Banned Our AI Manager from Writing Code and Assigned the Task to Claude Opus
The team behind an AI-powered marketplace manager for Wildberries initially built the system using regular updates, then migrated it to an autonomous agent. After implementing multiple layers of restrictions, they ultimately removed the agent entirely and rebuilt the solution from scratch. The new architecture relies on a single tool that handles the complete Wildberries API along with internet access while respecting all platform limits. The decision to prohibit the original AI manager from generating code stemmed from concerns over reliability and security in production environments. Instead, the developers turned to Claude Opus to handle coding tasks. This case highlights practical challenges of deploying AI agents in e-commerce automation and information security contexts.
Developer Builds MCP Linter and Discovers Security Issues in Anthropic Official Servers
A developer has released mcp-linter, a lightweight security and compliance tool for the Model Context Protocol used by Anthropic's Claude ecosystem. The linter detects critical problems such as stdout pollution that breaks JSON-RPC framing, missing destructiveHint annotations that allow autonomous agents to execute dangerous actions without human confirmation, prompt injection vectors hidden inside tool descriptions, and incomplete input schemas that increase model hallucinations. When run against Anthropic's reference servers, the tool assigned low health scores to server-memory and especially server-filesystem, highlighting dozens of parameters lacking descriptions. The utility runs with zero dependencies, supports SARIF output for GitHub Security, and can generate automatic JSON patches. The project is open source under MIT license and already integrates into CI pipelines via a dedicated GitHub Action.
Pentesting AI Components: Key Vulnerabilities CISOs Must Address in RAG and AI Agents
The article examines how AI integration into corporate systems dramatically expands the attack surface beyond traditional web application testing. It details risks associated with chatbots, RAG-enabled systems that pull from internal documents, and autonomous AI agents capable of executing real actions via APIs. Yuri Grishaev, an OSCP+ certified specialist and top Standoff 365 hacker, explains how prompt injection can bypass access controls and lead to data leaks or unauthorized operations. The piece stresses that service accounts often hold broad privileges, allowing AI components to serve as indirect paths to sensitive data even when direct user access is restricted. It also covers how AI-generated output can trigger classic vulnerabilities such as XSS if not properly sanitized. Recommendations include inventorying all AI tools, enforcing least-privilege principles, and validating user permissions before any model processes or acts on retrieved content. ABP2B provides free checklists and policy templates to help organizations prepare for secure AI adoption.