The Hacker News AI Security · July 28, 2026

Claude Mythos research prompts HAWK withdrawal and speeds a reduced-round AES attack

Why it matters

Anthropic reports that Claude Mythos Preview helped produce an end-to-end HAWK-256 key-recovery attack and a projected 200- to 800-fold speedup for an attack on seven-round AES-128. Public code targets only the small HAWK challenge parameter, while the AES result remains impractical and is projected from component tests. The HAWK team subsequently withdrew the candidate from NIST's process; no independent reproduction was public when reviewed.

My takeaway: Treat this as evidence of research acceleration and verification cost, not a break of production AES or lattice cryptography. Capability evaluations should separate end-to-end reproductions from projected components, record human and model labor plus compute, require external reproduction, and measure downstream impact—here, withdrawal of a standards candidate.
Keep exploring

More curated notes connected through Model Evaluation and AI Red Teaming.

OpenAI News · framework

OpenAI’s Frontier Governance Framework

OpenAI's 22-page Frontier Governance Framework maps its frontier-model processes to California's Transparency in Frontier AI Act and the EU AI Act's general-purpose AI code. It documents lifecycle risk assessment, cyber-offense and other risk tiers, mitigation and residual-risk decisions, critical-incident handling, security risk management, model reporting, external review, responsibility allocation, and change control.

OpenAI News · framework

Cybersecurity in the Intelligence Age

OpenAI proposes a five-pillar strategy for AI-enabled cyber defense: tiered access for trusted defenders, faster government-industry coordination, stronger protection of frontier models and infrastructure, risk-scaled deployment monitoring, and broader defensive support for individuals and small organizations.

OWASP GenAI Security Project · guide

OWASP Top 10 for Agentic Applications for 2026

OWASP's community guide organizes agentic-system risk into ten categories, including goal hijacking, tool misuse, identity and privilege abuse, memory poisoning, insecure inter-agent communication, cascading failures, and rogue-agent behavior. It provides a shared taxonomy and mitigation starting point rather than a certification checklist or evidence that a deployed system is secure.