Supply-Chain-Security

What Is an Agent Scanner for GitHub AI Agent Detection? An agent scanner for GitHub AI agent detection is a security tool that scans repositories to identify, inventory, and assess the security posture of autonomous AI agents, their skills, MCP server configurations, and tool permissions. These scanners emerged rapidly in 2026 after the ClawHavoc campaign planted over 1,200 malicious skills into agent marketplaces, and the market has since grown to over 95 open-source tools on GitHub. They serve as the first line of defense for organizations adopting AI agents at scale, enabling teams to detect shadow AI, enforce compliance with regulations like the EU AI Act, and prevent supply-chain attacks on agent ecosystems. ...

The Evolving Threat Landscape for npm in 2026 The npm ecosystem, with over 2.1 million packages and billions of weekly downloads, has become the most targeted open source registry for supply chain attacks. In 2026, the threat landscape has shifted dramatically from theoretical risks to active, sophisticated campaigns that exploit kernel-level vulnerabilities, AI toolchains, and CI/CD pipelines. The average data breach cost from compromised npm packages now stands at $4.5 million according to IBM’s 2024 Cost of a Data Breach Report. This figure reflects not just the immediate damage of a compromised dependency, but the cascading effects through downstream consumers, stolen credentials, and reputational harm. ...

If you maintain an open source project or review code on a team that uses AI coding tools, you’ve probably already seen it: a pull request that looks reasonable at a glance but has something subtly wrong. Maybe a variable name that doesn’t quite match the codebase conventions. A test that passes but doesn’t actually test the right thing. Or worse — a change that introduces a security vulnerability hidden inside otherwise clean code. This isn’t hypothetical. In 2026, AI agents cheating on pull requests is a documented, measurable problem, and it’s getting worse. ...

If your coding agents can’t see your artifact repository, they’re flying blind. They’ll guess dependency versions, hallucinate package names, and suggest upgrades that don’t exist. But giving an AI agent direct access to Artifactory is a bad idea — one prompt injection and your entire binary repository is an attack surface. JFrog solves this with two complementary paths: JFrog Skills (open-source agent skills) and the JFrog MCP Server (remote SaaS MCP server). Both give agents safe, governed access to artifact context, but they work differently and suit different use cases. Here is how both work, when to use each, and how to set them up without compromising security. ...

If your team is running AI coding agents in production — Claude Code, Cursor, Windsurf, GitHub Copilot — you’ve probably already felt the gap between traditional AppSec and what these agents actually do. Traditional security tools scan committed code. Agents don’t just write code; they install MCP servers, download skills, run shell commands, and make API calls. By the time a traditional SAST scan runs, the damage is already done. ...

Agent Skills supply chain security means treating every SKILL.md, referenced file, script, and marketplace update as executable influence over your AI agent. In practice, skills are closer to npm packages or CI actions than documentation, because a small metadata change can redirect planning, tool use, file access, and data movement. Why did Agent Skills become a supply chain problem in 2026? I’ve found that teams adopt Agent Skills for the same reason they adopted package managers: reuse beats rebuilding every workflow by hand. A skill can package conventions for code review, deployment, incident response, design handoff, or data analysis. The format is intentionally lightweight, which is exactly why it spreads quickly across tools such as Claude Code, OpenAI Codex, Cursor, GitHub Copilot, Gemini CLI, VS Code, Windsurf, and OpenClaw-style marketplaces. ...