Skip to content

AAK-AST02-001: Skill bundle pulls an external resource that nothing pins

Severity
HIGH
Category
Agentic Skills (AST10) (agentic-skill)
Scanner
agent_audit_kit/scanners/agentic_skills.py
Auto-fixable
No.
SARIF name
AgenticSkillUnpinnedExternalResource

What it detects

A skill bundle references an external resource with no content hash, commit SHA, integrity field or exact version anywhere in it: a git ref that moves (main, master, HEAD), a releases/latest redirect, a pipe-to-shell installer, or an unpinned package install. What the skill runs is then whatever that source serves at the moment it is used, and the skill itself never has to change for its behaviour to. This is OWASP AST02 Supply Chain Compromise together with the pinning half of AST07 Update Drift, whose own mitigation is stated as pinning to immutable content hashes rather than version ranges. The scale is why it is a rule rather than a lint: Air Security's Circus of Skills (2026-06-24) found 17,822 of 142,836 live skills, about 12.4% and 6.7M installs, resting on at least one untrusted external resource, and SkillJacking (2026-07-02) found 925 of them on sources that could be taken over outright — a deleted GitHub account re-registered, an expired domain — with no update event and no scanner alert.

How to fix

Pin every external resource the bundle reaches to something immutable: a commit SHA rather than a branch, a release asset with a recorded sha256: rather than releases/latest, an exact package version rather than a range. If the resource is a script fetched at run time, vendor it into the bundle so review and pinning apply to it. Pinning is what makes a later change reviewable; without it an upstream takeover reaches you on next use rather than on next upgrade.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-AST02-001

Limitations

Static, and scoped to what a skill bundle declares on disk. It cannot see a resource that is pinned at install time by tooling outside the bundle, and it does not fetch anything, so a pinned reference that now resolves elsewhere looks the same as one that does not. It reports a bundle only when nothing in it is pinned, so a bundle that pins its dependencies and floats one script is not reported — that keeps the rule quiet on ordinary projects at the cost of missing partial pinning. It reads the shapes listed above and will miss an unpinned resource fetched through an indirection it cannot follow.

References


All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-AST02-001.md: the page then shows that text, with the registry reference appended under it.