Microsoft separates two supply-chain threats: malicious examples in a victim’s fine-tuning data and attacker-trained model checkpoints. Its experiments show triggered tool misuse can survive later training and transfer across repositories or harnesses, with substantial variation between settings. Both require compromise of training artifacts; the results do not establish a flaw in a coding tool’s default model configuration.
Poisoned agent training: test the model and enforce tool boundaries
Related research
More curated notes connected through Adversarial ML and Agent Security.
Pacing model development in an era of cyber-critical capabilities
OpenAI says preliminary evidence that Astra may meet its Critical cybersecurity threshold led it to pause frontier reinforcement-learning work for two weeks and keep its largest planned run on hold. New safeguards include stronger workload and network isolation, continuous boundary testing, token-level monitoring that escalates suspicious tool activity, and broader alignment checks for deception, reward hacking, and unauthorized access.
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.
A blueprint for democratic governance of frontier AI
OpenAI proposes a three-part U.S. frontier-AI governance model: harmonize emerging state safety laws into a federal baseline, strengthen CAISI as an evaluation and standards institution, and coordinate a broader resilience program. Proposed controls include severe-risk evaluations, transparency reports, independent audits, safety-incident reporting, model-weight security, whistleblower protection, and periodic technical assessments.