AI Red Team Engineering notes, research references, and field notes on AI systems, responsible AI, governance, and compliance.
Global search

Search AI Red Team

Search across the complete knowledge base.

Enter at least two characters to begin.
↑↓ select Enter open Browse the full research archive
The Hacker News AI Security · September 2, 2026

GitSpawn: background Git calls bypass coding-agent approval boundaries

analysis Agent SecurityAI Red TeamingAI Engineering
Why it matters

Manifold’s GitSpawn research traces eight findings across seven coding agents to background Git calls that honor executable repository configuration. Some calls run before workspace trust or outside the agent sandbox. The delivery condition is a directory or archive containing attacker-controlled .git metadata; ordinary clone, fetch and pull do not transport that configuration. Four findings remained unpatched in the researcher’s September 1 retest.

My takeaway: Include startup, context gathering and review helpers in the agent threat model. Inspect received repository metadata before opening it, sanitize executable Git configuration on background calls, and test that all helper processes respect trust and sandbox boundaries. Verify fixes per execution path rather than assuming one patched Git setting covers every variant.
Keep exploring

More curated notes connected through Agent Security and AI Red Teaming.

OpenAI News · framework

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 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.

OpenAI News · framework

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.