17,800 AI Add-Ons Take Orders From Sources Nobody Verified. Now the Endpoint Can Block Yours

Surya Pratap
By Surya Pratap

September 7, 2026

11 min read

AI & Technology
The two launches of 1 September 2026 set side by side — on the left the supply chain, with 17,800 public AI add-ons drawing on unverified instruction sources across 6.7 million installations, skills impersonating Anthropic and OpenAI able to run arbitrary code and 27% of what was discovered filtered back out, and on the right what the endpoint can now do, inventorying every running and dormant agent, tracing prompt to identity to tool call to system action, and blocking any agent nobody approved, on Windows and macOS at runtimeThe supply chain, and the new gateHover to explore
One launch says what agents are quietly loading. The other says the machine can now refuse. They shipped on the same day, which is the part worth noticing.

Most weeks the agent news is a capability. This week it was a gate.

On 1 September, two things launched within hours of each other. CrowdStrike unveiled Falcon Guardian, which inventories every AI agent running on a machine — including the ones nobody registered — and blocks the agents nobody approved. And AIR Security came out of stealth with $50 million to build an inline firewall that screens what enters an agent's context before the agent acts on it.

Read separately, two product announcements. Read together, they are the same sentence from both ends: agents are now arriving in companies faster than anyone can account for them, and the response has moved from policy to enforcement.

1. What actually shipped

Two launches, 1 September 2026

One built to see and stop agents, one built to check what they load

  • Falcon Guardian discovers known and shadow AI agents across Windows and macOS, producing a live inventory of every running and dormant agent — and who deployed it.
  • It traces the execution chain from prompt and identity through tool call to every downstream system action, rather than treating the agent as one opaque process.
  • Its access controls define which agents may run on managed endpoints and block the ones that are not approved, at runtime.
  • AIR Security launched with $50 million across two rounds — $10M led by Sequoia, then $40M led by Greenoaks — for a company founded earlier this year with roughly 40 people.
  • Its firewall screens the instructions, tools and data heading into an agent's context, not just what the agent is permitted to do afterwards.
  • Its research found 17,800 public AI add-ons across 6.7 million installations drawing on unverified external instruction sources, including skills impersonating Anthropic and OpenAI that could run arbitrary code.

Note who is buying. AIR reports 20-plus companies already using the platform, about a quarter of them large enterprises, with the strongest demand from financial services and pharma. Those are the two industries that historically decide what everyone else's procurement looks like eighteen months later.

2. The phrase that should stop you

Not the funding. Not the enforcement. This one:

Shadow AI agent. Known and shadow, across Windows and macOS.

"Shadow AI agent" is now a named category inside a security product, with a live inventory attached and a block button next to it.

That phrasing has a history. "Shadow IT" was what the industry called bottom-up SaaS adoption for a decade — and bottom-up SaaS adoption was, for that same decade, the single most reliable distribution strategy a software founder had. You did not sell to the CIO. You got installed by the person who needed the thing, and by the time procurement noticed, you had four hundred seats and an internal champion.

Every agent startup I know is running some version of that playbook right now. An engineer installs your CLI. A team wires up your MCP server. Nobody files a ticket.

The uncomfortable symmetry

A product now exists whose explicit job is to produce a list of exactly those installs, name the person who deployed each one, and stop the ones that were never approved. Your distribution strategy and its detection logic are describing the same event. That does not mean you are the threat it was built for — but the inventory does not know that on day one, and neither does the security analyst reading it.

3. The 17,800 is a different problem than it looks

It is easy to read AIR's number as a story about bad actors publishing malicious skills. Some of it is: fake add-ons wearing Anthropic and OpenAI branding to get past review is straightforwardly an attack.

But most of 17,800 is not malice. It is add-ons that fetch their instructions from somewhere else at runtime — a URL, a repo, a hosted config — because that is a perfectly sensible way to ship updates without republishing. The supply chain is doing what supply chains do.

The problem is what that means once an agent is on the other end. A library you install executes the code you audited. An add-on that pulls instructions at runtime executes text that arrives later, inside a context window that has your credentials and your tool permissions attached to it. It is not a dependency in the sense your dependency scanner understands. It is an open channel into the part of your system that acts.

I wrote about the identity half of this when the MCP roadmap started designing the human out of the loop. This is the other half: not who the agent is, but where its instructions came from.

4. If you ship an agent into enterprises

You will be found

Assume
The premise that quiet installs stay quiet has an expiry date, and on Windows and macOS endpoints it has arguably passed. Plan for the conversation where a security team already has your name, the machine count, and the person who installed you. Being discovered is now the normal case, not the failure case.

The approval artefact early

Ship
What gets you onto an allowlist is boring and specific: what your agent runs as, what it reads, what it can call, what leaves the machine, how it updates. If a security reviewer has to reverse-engineer that from your binary, you are a finding. If you hand it over on request, you are a vendor.

Runtime instruction fetching

Kill
If your product pulls prompts, skills or tool definitions from your servers after install, you are the 17,800. There may be good reasons for it, but it makes you indistinguishable from the thing the firewall exists to catch. Version it, sign it, ship it with the release.

Bottom-up as the only motion

Rethink
Bottom-up still works to prove demand. It no longer works as the whole path to a contract, because the step where nobody notices is now instrumented. Land bottom-up, but build the approval path deliberately instead of hoping the champion carries you through it.

5. If you consume third-party skills and MCP servers

The same research is a warning pointed the other way. Most founders shipping agent products are also, quietly, running twenty of somebody else's add-ons in their own stack.

What you have actually installed

Inventory
Ask your team for the list of MCP servers, skills and plugins connected to anything with production credentials. The list is almost always longer than the founder expects, and nobody owns it, because installing one takes ten seconds and looks like configuration rather than a dependency.

Code you audited from text that arrives

Separate
Treat an add-on that fetches instructions at runtime as an untrusted input path, not as a library. The useful question is not "is this package popular" but "what can this thing say to my agent tomorrow that it did not say today, and what would my agent do about it."

Blast radius before trust

Bound
Scoped credentials and a separate execution context beat vetting, because vetting is a point-in-time claim about a channel that stays open. Assume one add-on eventually goes bad and make that survivable rather than trying to guarantee it never happens.

The full forensic timeline of the OpenAI agent breach is the version of this that already happened, and the shape was the same: the agent was not compromised, the thing it trusted was.

6. What I would not conclude

This is not the end of bottom-up. Enforcement is a capability that has to be turned on, tuned, and staffed. Most companies will run discovery for a long time before they run blocking, because a false positive that kills an engineer's coding agent is an expensive ticket. The inventory arrives well before the block does.

Two launches on one day is a signal, not a market. Vendors cluster announcements around conferences, and Fal.Con was that week. What makes it worth writing about is that one is an incumbent adding enforcement and the other is a six-month-old company raising $50 million on the same premise — but that is still two data points, and I am reading a direction into them.

AIR's 17,800 is their own research. It comes from a company selling the solution to the thing it measured, which does not make it wrong — the impersonation finding is concrete and checkable — but the framing of what counts as "untrusted" is theirs, and the 27% filter rate suggests the raw number was noisier still.

The honest summary

The interesting thing about 1 September is not either product. It is that the question changed from "can agents be trusted" to "which agents are running here, who put them there, and should they be". That is an operational question, and operational questions get answered by tools, and tools get bought.

For founders shipping agents, the practical shift is small and annoying: the moment where nobody noticed you was load-bearing, and it is being instrumented away. What replaces it is not worse, just slower and more explicit — an approval artefact, a named owner, a scope you can describe in one page.

For founders running agents, the shift is larger. Your dependency list is now also an instruction list, and the second one was never reviewed by anyone. 17,800 add-ons and 6.7 million installations is not a story about other people's security posture. It is a decent estimate of how many of those channels are open inside ordinary companies right now, including yours.

Sources: CrowdStrike press release, "CrowdStrike Unveils Falcon Guardian to Secure AI Agents Where They Execute" · SiliconANGLE on Falcon Guardian · SiliconANGLE on AIR Security's launch · SecurityWeek on the AIR Security round · Product capabilities, funding and research figures are as reported; the distribution argument and the cautions in section 6 are mine.

IdeaToMVP Academy

Want to build with AI — not just read about it?

4-week live cohort for founders. Learn to ship AI agents, scope MVPs, and automate your business — taught by the same team that writes these guides.

Explore the Academy →
Share this post :