AI-Generated Code Security Risks From an AI-Assisted Rebuild

An HTTP 500 Internal Server Error page filling an entire website, the kind of AI-generated code security risk a single bad configuration line can cause.

Over six weeks I rebuilt a 30-year-old poetry site with an AI coding partner and logged every security issue it produced: 59 of them, from a one-line config change that took the whole site down to a 90-minute triple credential leak. Two became actual incidents; a control caught all 59. Here is the pattern behind them, Self-Attested Safety, and the controls that caught every one.

Your AI Safety Tool Evaluates Text, Not What Users See — Here’s Why It Matters

Conceptual illustration of an open book where each page shows the same text rendered differently, with a magnifying glass revealing only one interpretation

Every major AI assistant endorsed a webpage as safe while it displayed a reverse shell command to the human reader. No bug. No jailbreak. A custom font and standard CSS were enough. The flaw is an architectural blind spot — a rendering-layer trust boundary no AI safety framework has ever specified — and it changes the threat model for every product team building AI-assisted content evaluation.