Adversarial Input

ippsec, odie, and purestruggle open on the pre-auth RCE in WordPress Core and how quickly everyone pointed their models at the SQL injection behind it. Then: living with Fable's cyber guardrails, whether any of them still read AI-written code, Kimi K3 closing the open-weight gap, the export-control argument, Meta's return, and Grok Build shipping whole git repositories to a cloud bucket....

In Episode 3, ippsec, odie, and purestruggle break down what AI “loops” look like in practice: long-running research agents, issue-board orchestration, explicit goals, memory files, and the state tracking needed to understand work completed while no one is watching. They compare frontier and open-weight models, debate cost and benchmark hype, and explain why planner-worker routing can outperform u...

Episode 2 of Adversarial Input dives into the fallout from Fable 5 access, Mythos restrictions, and the growing tension between frontier AI capability and cybersecurity guardrails. ippsec, odie and struggs compare hands-on impressions, debate whether "unjailbreakable" models are realistic, and weigh the privacy tradeoffs of identity verification for advanced model access. They also dig i...

Nick, Ryan, and Matt launch Adversarial Input with one question: what could AI do that would actually scare them? That sends them through voice-cloned scam calls, the Glasswing report, and Mythos, the security model that runs five to ten times the cost of Opus. They dig into why the harness around a model matters as much as the model itself, why fewer than 1% of AI-found bugs ever get patched, and...