T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:237- Finding
Unpinned Remote Skill Installation Allows Post-Audit Payload Changes
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:237-251
Vulnerability Type: Unpinned installation of mutable remote Skill repositories
Risk Level: MediumVulnerable Code
bash # Install web123 itself / 安装 web123 openclaw skill install https://github.com/AntalphaAI/web123 # Single skill / 安装单个 openclaw skill install https://github.com/AntalphaAI/web3-trader # 新手包 / Beginner pack openclaw skill install https://github.com/AntalphaAI/wallet-balance https://github.com/AntalphaAI/web3-trader https://github.com/AntalphaAI/transaction-receipt # 交易套装 / Trading pack (v1.1 new) openclaw skill install https://github.com/AntalphaAI/web3-trader https://github.com/AntalphaAI/cex-trader https://github.com/AntalphaAI/TA-Radar # 数据情报套装 / Data intel pack (v1.1 new) openclaw skill install https://github.com/AntalphaAI/smart-money https://github.com/AntalphaAI/crypto-social-intel https://github.com/AntalphaAI/TA-RadarEquivalent unpinned commands also appear in
README.md:17,README.md:60-78,README.md:127,README.md:170-188, and throughoutreferences/skills.json:47-344.Technical Analysis
The Skill generates installation commands that retrieve other Skills directly from mutable GitHub repository URLs. The URLs do not specify immutable commit hashes, signed release tags, version constraints, or integrity digests.
Consequently, the content installed by a command can differ from the content that existed when this navigator was reviewed. Although all listed URLs use the same stated GitHub organization and no malicious upstream content was present in the audited project, the external repositories are not included in the audit scope and their future contents cannot be guaranteed.
This is best classified as remote payload retrieval because execution of the suggested installation command fetches externally controlled Skill content whose effective payload may change after review.
Attack Path
...[truncated 1544 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin every recommended repository to a reviewed immutable commit hash or cryptographically signed release.
- Extend
references/skills.jsonwith explicit version, commit, and integrity-digest fields instead of storing only mutable repository URLs. - Verify the resolved revision and integrity digest before installation, and reject content that does not match the approved metadata.
- Display the repository, revision, requested permissions, and verification status before installation.
- Require explicit user confirmation before installing any remote Skill, particularly trading, wallet, payment, API-key, or signing-related Skills.
- Maintain an allowlist of reviewed repository revisions and periodically re-audit dependencies before approving newer versions.
- Prefer a trusted registry or release-artifact mechanism that supports signatures and reproducible integrity verification.
