The Hacker News AI Security · August 4, 2026

Keyv-Linked npm Worm Poisons Hundreds of Packages, Plants Claude Code and VS Code Hooks

Why it matters

A credential-stealing npm worm spread through hundreds of package versions using lifecycle scripts and a Bun-based payload. Related repositories also carried Claude Code and VS Code hooks that could execute after workspace trust; reported campaign totals vary, so exposure depends on exact resolved versions and execution.

My takeaway: Treat environments that executed affected releases as credential-exposed. Remove the malware's credential-revocation watcher before rotating secrets, verify lockfiles and resolved versions, disable unnecessary install scripts, and audit trusted agent and editor hooks as executable supply-chain code.
Keep exploring

More curated notes connected through Agent Security and AI Engineering.

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.

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.

OECD.AI Wonk · guide

A five-step roadmap to closing the AI evaluation gap

The roadmap addresses evaluation results that overstate real-world performance or fail to transfer across deployment contexts. Its five steps balance standardized and local tests, evaluate throughout the lifecycle, build qualified assurance and communication capacity, tailor tests to each value-chain actor and technology, and use a coordinated, trusted process for updating methods.