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
SecurityWeek AI Security · August 14, 2026

Trivy, Not LiteLLM Behind the 2,500 Org Compromise

news Agent SecurityAI EngineeringAI Compliance
Why it matters

SecurityWeek reports that updated exposure analysis shifts the dominant source of the TeamPCP blast radius upstream from the malicious LiteLLM releases to the earlier Trivy supply-chain compromise. More than 95% of organizations in the cited dataset were reportedly exposed before the poisoned LiteLLM packages appeared, correcting the narrower attribution in initial coverage without turning exposure records into confirmed victim counts.

My takeaway: Expand incident scope beyond hosts that installed LiteLLM 1.82.7 or 1.82.8. Identify every CI job, image, cache, and workstation that ran affected Trivy artifacts or mutable actions; revoke every reachable secret; rebuild from trusted inputs; and verify package-publishing credentials downstream. Keep dataset matches, successful exfiltration, and confirmed compromise as separate evidence states.
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.