Show Notes
In this episode of BHIS Presents: AI Security Ops, the team breaks down the LiteLLM supply chain compromise–a real-world attack that shows how AI systems are being breached through the same old software supply chain weaknesses. What initially looked like a bad release quickly escalated into a full-scale compromise affecting a library downloaded millions of times per day. But LiteLLM wasn’t the starting point–it was just one link in a much larger attack chain involving compromised security tools, CI/CD pipelines, and stolen publishing credentials. The result? Malicious packages distributed at scale, harvesting secrets, enabling lateral movement, and establishing persistence across affected systems. We dig into: • What LiteLLM is and why it’s such a high-value target • How the attack chain started with compromised security tooling (Trivy, Checkmarx) • How unpinned dependencies enabled the compromise • The role of CI/CD pipelines in exposing sensitive credentials • What the malicious LiteLLM packages actually did (credential harvesting, persistence, lateral movement) • The scale of impact given LiteLLM’s widespread adoption • Why supply chain attacks are no longer theoretical–and no longer nation-state exclusive • How AI is lowering the barrier to entry for attackers • Why this wasn’t really an “AI vulnerability”–but an infrastructure failure • The growing risk of automated, agent-driven attack discovery This episode highlights a critical reality: the biggest risks in AI systems aren’t always in the models–they’re in the pipelines, dependencies, and infrastructure surrounding them. ⸻ 📚 Key Concepts & Topics Supply Chain Security • Dependency poisoning and malicious package distribution • CI/CD pipeline compromise • Version pinning and build integrity Credential & Secrets Exposure • API keys, SSH keys, and cloud credentials in pipelines • Risks of centralized AI gateways like LiteLLM Threat Actor Techniques • Tag rewriting and trusted reference hijacking • Multi-stage malware (harvest, lateral movement, persistence) • Use of lookalike domains for exfiltration AI & Security Reality Check • AI as an amplifier, not the root vulnerability • Traditional security failures in modern AI stacks • Automation lowering attacker barriers Defensive Strategies • Dependency pinning and isolation (Docker, VPS) • Atomic credential rotation • Treating CI/CD tools as critical infrastructure • Monitoring outbound traffic from build environments
(00:00) - Intro & Incident Overview
(01:26) - What Is LiteLLM & Why It Matters
(03:53) - Supply Chain Scope & Why This Is Dangerous
(07:31) - Why These Attacks Are Getting Easier (AI + Scale)
(10:48) - Attack Chain Breakdown (Trivy → Checkmarx → LiteLLM)
(11:50) - What the Malware Did & Impact at Scale
(14:23) - Detection, Response & Who Was Safe
Click here to watch this episode on YouTube.
Creators & Guests
Brian Fehrman - Host
Bronwen Aker - Host
Derek Banks - Host
Brought to you by: Black Hills Information Security https://www.blackhillsinfosec.com
Antisyphon Training https://www.antisyphontraining.com/
Active Countermeasures https://www.activecountermeasures.com
Wild West Hackin Fest https://wildwesthackinfest.com 🔗 Register for FREE Infosec Webcasts, Anti-casts & Summits https://poweredbybhis.com Click here to view the episode transcript.
More from AI Security Ops
In this episode of BHIS Presents: AI Security Ops, the team digs into some of the strangest recent examples of AI behaving badly. An AI agent finds a way around its sandbox using DNS. Malware asks four different AI models what it should do next. Attackers overwrite an AI agent’s “soul.” And a placeholder domain buried across GitHub becomes an unexpected security risk. Funny stories? Absolutely. But underneath them are some very familiar security problems. We dig into: - An OpenAI agent finding an unexpected path out through DNS - Whether a 2.5-hour response is fast enough in the age of AI - CLOSEDQUORUM malware using multiple AI models to make decisions - Why outbound AI API traffic could become a useful detection signal - The Carbonado botnet rewriting an agent’s SOUL.md instructions - The risks of exposed Docker daemons - How an unreserved placeholder domain can become an attack vector - Why AI agents make old security mistakes more consequential The takeaway: none of these techniques are particularly new. DNS tunneling, exposed services, compromised configuration files, and untrusted domains have existed for years. AI just gives attackers — and occasionally AI agents themselves — new ways to find and exploit those boring gaps at greater speed and scale. 2026-09-29-News (1).docx (00:00) - Intro: AI Behaving Badly
In this episode of BHIS Presents: AI Security Ops, the team continues its breakdown of the OWASP Agentic Skills Top 10, covering risks six through ten. Agentic skills may look like simple instructions, but they operate inside AI systems with access to tools, files, networks, and other resources. So what happens when those skills aren’t isolated, verified, monitored, or governed? We dig into: - AST06: Weak Isolation - AST07: Update Drift - AST08: Poor Scanning - AST09: No Governance - AST10: Cross-Platform Reuse - Why sandboxing the agent isn’t the same as isolating individual skills - The security tradeoffs between automatic updates and outdated skills - Why traditional scanners struggle with malicious instructions written in plain English - The importance of maintaining an inventory of agentic skills - How security controls can disappear when skills move between platforms The takeaway: securing agentic skills requires more than checking them once before installation. Organizations need visibility into what skills are running, what they can access, how they change, and whether their security controls survive across environments. OWASPAgenticSkils-Part2.docx This is Part 2 of our look at the OWASP Agentic Skills Top 10, covering AST06 through AST10. Part 1 can be found here #AISecurity #CyberSecurity #AgenticAI #AIAgents #OWASP #LLMSecurity #InfoSec #BHIS #Antisyphon
In this episode of BHIS Presents: AI Security Ops, the team tackles a big question: Could AI actually take over the internet? Recent warnings from AI industry leaders have raised concerns about autonomous agent swarms escaping containment, compromising systems, and operating at a scale humans may struggle to match. But what would “taking over the internet” actually require? The team looks at the problem from a hacker’s perspective — examining compute requirements, persistence, botnets, vulnerable infrastructure, the recent Hugging Face incident, and the difference between AI acting autonomously and humans using AI to accelerate attacks. We dig into: - Whether an autonomous AI swarm could realistically operate at internet scale - What the Hugging Face incident actually tells us about agentic security - The compute and infrastructure required to sustain a rogue agent swarm - How botnets and compromised systems could change the equation - Why existing vulnerabilities may be a bigger concern than hypothetical AI takeover scenarios - Whether slowing frontier AI development actually addresses the cybersecurity problem - The difference between AI exhibiting dangerous behavior and AI having intent - Why defenders need to focus on their real-world attack surface today The takeaway: AI is dramatically increasing the speed and scale of cybersecurity operations, but powerful models still operate inside systems designed, deployed, and connected by people. The immediate security question may be less “Will AI take over?” and more “What are we giving AI access to?”
In this episode of BHIS Presents: AI Security Ops, the team breaks down the first five risks in the OWASP Agentic Skills Top 10 (Part 1). Agentic skills can give AI systems reusable instructions, workflows, and capabilities — but they also introduce a new attack surface. A skill may look like a simple markdown file, yet the agent following those instructions could have access to your filesystem, credentials, network, shell, or other sensitive resources. We dig into: - AST01: Malicious Skills - AST02: Supply Chain Compromise - AST03: Overprivileged Skills - AST04: Insecure Metadata - AST05: Untrusted External Instructions - Why skills should be treated more like software than configuration - How excessive permissions increase an agent’s blast radius - Why external content creates indirect prompt injection risks - How isolation, least privilege, and trusted sources can reduce risk The takeaway: “just markdown” isn’t necessarily harmless when an AI agent can act on what it reads. This is Part 1 of our look at the OWASP Agentic Skills Top 10, covering AST01 through AST05. — Learn more about Black Hills Information Security: https://www.blackhillsinfosec.com/ Check out Antisyphon Training: https://www.antisyphontraining.com/ (00:00) - Intro: OWASP Agentic Skills Top 10, Part 1
Agentic skills can make AI agents more capable and consistent—but they can also introduce serious security risks. This episode explains how skills work, why malicious skills rank as a leading OWASP concern, and how seemingly harmless Markdown instructions can enable credential theft, remote payload delivery, and manipulated recommendations. Real-world examples illustrate how malicious skills can evade scanners and exploit trusted marketplaces. The episode concludes with practical safeguards, including reviewing skill files, watching for external instructions and prompt injection, pinning versions, limiting permissions, and running agents inside isolated environments. Links: OWASP Agentic Skills Top 10 Malicious AI Agent Skill Bypasses Security Scans and Seizes Full Control of Over 26,000 Agents (00:00) - Agentic Skills and the OWASP Top 10