Join our Newsletter — 33% off our NHI Course

Who is exposed when curl | bash runs with delegated credentials?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20225
Topic starter  

TL;DR: AI agent installs through curl | bash become riskier when the runtime actor can keep acting with delegated credentials after the fetch, according to Manifold Security. Runtime behaviour now matters more than the installer alone for judging whether the session stayed benign.

Editorial analysis by NHI Mgmt Group, based on content published by Manifold Security: “What to Think About curl | bash Now That AI Agents Run It.”.

By the numbers:

  • The search across 2.7 million events from four internal agent instances flagged 3,299 events, but at most 73 were real commands, roughly 2 percent.
  • A plain text search for the download-and-run pattern produced about 98 percent false alarms in Manifold Security's sample.
  • Scanner coverage of the 855 public skills found a real download-and-run command in each reviewed skill set, with Manifold's allowlist adding another 17 percent of verified installers.

Key questions

Q: Why do trusted domains create extra risk for AI agent security?

A: Because trust can be inherited by content that was never meant to deserve it.

Q: How should security teams monitor agent installs after the download?

A: Track the agent's actual behaviour after the fetch, including tool execution, file reads and writes, and outbound calls.

Q: What breaks when AI agents use curl | bash to install tools?

A: The main failure is that the installer is no longer a human-reviewed action with a stable payload.

Practitioner guidance

  • Define agent installer trust boundaries Classify which agents may execute remote installers, which may only read them, and which must be blocked from fetch-and-execute paths entirely.
  • Require provenance over bare URLs Pin releases to signed artefacts or verified hashes instead of latest tags, and reject installers that depend on mutable remote content.
  • Log the full post-fetch session Capture the tools the agent ran, files it touched, and outbound requests it made after download so the runtime intent is visible.

Bottom line: AI agents turn a familiar insecure install pattern into an identity-governance issue because the runtime actor can keep acting with delegated credentials after the fetch.

Glossary terms: Fetch-and-execute, Conditional payload delivery, Runtime Identity, Provenance Validation

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20715
 

Credentialed fetch-and-execute is now an identity problem, not just a software hygiene problem. The article shows that the same install pattern becomes materially different when the executor is an AI agent with delegated access and follow-on tool authority. That changes the control question from whether the script is readable to whether the runtime identity should be allowed to fetch, interpret, and act on remote code at all.

A few things that frame the scale:

A question worth separating out:

Q: Should organisations allow AI agents to run remote installers at all?

A: Only when the task scope, provenance checks, and runtime logging are strong enough to make the trust decision explicit. If an agent can install, re-fetch, and act on remote code with broad credentials, the organisation is accepting a moving trust boundary that is difficult to audit and hard to contain.

👉 Read our full editorial: Curl | bash becomes a credential risk for AI agents


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.