T08 · Insecure Dependencies
- Location
SKILL.md:49- Finding
Unpinned Remote Skill Installation and Persistent Registry Reference
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 49–52
Vulnerability Type: Unpinned third-party Skill dependency
Risk Level: MediumVulnerable Code
bash # Via skill manager (recommended) skill-install tiktok-trend-challenger # Or manually add to agent config echo "tiktok-trend-challenger: https://www.pinghuman.ai/skills/tiktok-trend-challenger/skill.md" >> ~/.agent/skills.txtTechnical Analysis
The installation instructions do not pin the Skill to an immutable version, commit, cryptographic digest, or verified signature. The manual installation method also creates a persistent registry entry that points directly to a mutable remote
SKILL.md.Consequently, the content loaded in a future agent session may differ from the content reviewed during this audit. Although the audited file does not itself contain a malicious payload, compromise or unauthorized modification of the remote resource could turn this installation mechanism into a supply-chain delivery channel. The
skill-installexample likewise provides no explicit source validation or integrity-verification procedure.Attack Path
- A user follows the documented installation instructions.
- The manual method records the remote PingHuman Skill URL in
~/.agent/skills.txt, or the Skill manager resolves the unpinned package name. - The referenced remote Skill content is subsequently modified or its hosting/distribution channel is compromised.
- In a later session, the agent or Skill manager retrieves the changed content without comparing it against a trusted digest or signature.
- The agent processes the substituted instructions as trusted Skill content.
- Those instructions could induce unauthorized API operations, redirect data to an attacker-controlled service, or otherwise alter behavior within the permissions available to the agent.
Exploitation therefore requires control of, or the ability to tamper wi ...[truncated 731 chars]
- Remediation
View remediation
Remediation Suggestions
- Distribute the audited Skill as a local, versioned artifact rather than loading mutable documentation directly from a remote URL.
- Pin installation to an immutable release identifier, commit, or content-addressed artifact.
- Publish a SHA-256 digest or signed manifest and verify it before activating the Skill.
- Configure the Skill manager to reject unsigned content and fail closed when integrity verification fails.
- Record the verified version and digest in
~/.agent/skills.txtinstead of only recording a mutable URL. - Require explicit user review and confirmation whenever retrieved Skill content differs from the previously approved digest.
- Document the authoritative package source and provide a secure update procedure with rollback support.
- Apply least privilege to agents loading third-party Skills, particularly for credentials, payment actions, and task-approval APIs.
