A special topic episode covering the most consequential AI platform security incident disclosed to date — now updated with state-sponsored threat context and NDAA policy deadlines.

On March 9th, 2026, an autonomous offensive security agent compromised McKinsey's internal AI platform Lilli in approximately two hours. The entry vector was SQL injection — a vulnerability class from the 1990s — through 22 unauthenticated API endpoints. No credentials were used. No zero-day exploits were required.

What was exposed: 46.5 million chat messages in plaintext. 728,000 files including strategy documents and M&A analysis. 57,000 user accounts. 3.68 million RAG document chunks with S3 storage paths. And 95 writable system prompts across 12 model types — the ability to silently alter AI behavior flowing to approximately 40,000 consultants without any code deployment.

This episode walks through the full attack chain, gives the skeptical view fair treatment (including security analyst Edward Kiledjian's detailed critique), maps the incident to OWASP Web Top 10, OWASP LLM Top 10, NIST AI RMF, and ISO 42001 controls, and provides a seven-point enterprise AI security checklist.

New in this edition: how the same elementary vulnerabilities that enabled the Lilli breach are being exploited by state-sponsored actors — Iranian APT groups integrating AI into offensive operations, the Stryker wiper attack, AWS data center drone strikes during Operation Epic Fury, and FY2026 NDAA AI governance deadlines including the April 1st AI Futures Steering Committee.

This is one of more than 20 documented AI platform security incidents since January 2025. The pattern is consistent: the AI is new, the security failures are not.

27 sources cited. Full source list in show notes.

AI Disclosure: This episode was produced with AI assistance. Research synthesis and script writing used Claude (Anthropic) under human editorial direction. Audio narration by Microsoft Edge TTS (en-US-AndrewNeural voice).

The AI industry spent 2025 moving fast. This episode is about what broke — and why the real danger isn't the technology itself.

AI-generated code now creates 1.7x more issues than human-written code in production. Security flaws appear in 45% of AI-generated output. AI-generated code is now the cause of 1 in 5 breaches. Pull requests per author increased 20% — but incidents per pull request grew 23.5%. The productivity gains are real. So is the quality deficit.

But models have improved from 4.4% to 81% on SWE-bench in three years. Developer satisfaction is up, burnout is down 17%, and the improvement trajectory is steep. The defect data from 2025 is already narrowing. Survey results showing 96% distrust deserve context: 89% of all workers fear AI's impact on their jobs, and displacement anxiety colors how developers evaluate the tools that might replace them.

The real danger isn't the technology — it's the incentive structures around it. 88% of executives are increasing AI budgets. 53% of investors expect ROI in 6 months. Nearly half of respondents acknowledge returns fall short. Quick wins and press releases can hide a corrosive culture that sacrifices quality, security, and sustainability for speed and optics.

Key finding: enterprises where senior leadership actively shapes AI governance achieve significantly greater business value. Only 1 in 5 companies has a mature governance model for autonomous AI. Executive teams must roll up their sleeves and be involved. This technology demands it.

Over 50 sources cited. Full source list in show notes.

AI Disclosure: This episode was produced with AI assistance. Research synthesis and script writing used Claude (Anthropic) under human editorial direction. Audio narration by Microsoft Edge TTS (en-US-AndrewNeural voice).

A comprehensive landscape assessment of AI coding agent governance. 85% of

developers use AI coding tools. 41% of all code is AI-generated. Only 6% of

organizations have an advanced AI security strategy.

This episode maps the full attack surface: AI coding agents (GitHub Copilot,

Claude Code, Cursor at $9B valuation), MCP protocol security (30 CVEs in 60

days, 38% of servers lack authentication, 43% vulnerable to command execution),

model provenance gaps (multi-model routing, Chinese-origin data residency risks),

and real-world exploitation incidents — CVE-2025-6514 MCP supply chain RCE,

Supabase/Cursor breach, IDEsaster (24 CVEs across all major coding tools),

RoguePilot repository takeover, EchoLeak zero-click M365 Copilot exfiltration,

UNC6395/Drift 700-customer compromise, plus this week's disclosures including

MS-Agent CVE-2026-2256, PleaseFix, OpenClaw, and Rules File Backdoor.

Plus: FOMO-driven adoption analysis (stock price pressure, funding optics),

IBM shadow AI data (20% of all breaches, $4.63M average), EU AI Act August

2026 enforcement, and a four-item practitioner playbook.

The U.S. government just designated an American AI safety company as a supply-chain risk to national security — for refusing to remove its guardrails. In this inaugural episode: MCP's 97 million SDK downloads with zero security standards, AI-enabled attacks hitting 29-minute breakout times, three compliance deadlines converging by August, Google API keys quietly gaining AI access, and the largest AI-justified layoff in history.