T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:10- Finding
Installation and Execution of Mutable, Unaudited Remote Code
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 10-14
Vulnerability Type: Remote payload retrieval and execution
Risk Level: HighVulnerable Snippet
text ## 使用指南(以hermes agent为例) 1. 加载skill。下达指令,“安装skill,https://github.com/zify9000/weibo-hot-with-your-taste”; 2. 配置凭证。下达指令,"配置微博热点skill", 交互式完成初始化配置(提供LLM和飞书凭据,扫码登陆微博,访谈用户偏好形成特征规则); 3. 设置定时任务,下达指令,“每小时执行一次微博热点爬取,12点05,18点05各执行一次推送,每周执行一次偏好特征优化(编写sh脚本,使用no_agent模式执行)”; 4. 触发式调用,下达指令,“抓取并推送微博热点”,“对话题1/3不感兴趣”,“展开说说话题2和话题3”,“进行一轮微博热点偏好调研”。Technical Analysis
The audited package contains only
SKILL.md; none of the referenced scripts are included. The instructions direct the Agent to install the effective implementation from a personal GitHub repository and then configure it with LLM, Feishu, and Weibo credentials.The repository URL is not pinned to an immutable commit, signed release, or verified checksum. Consequently, the code ultimately executed can differ from the artifact reviewed here and can change after approval. The absence of local scripts also prevents verification of network destinations, transmitted fields, command construction, credential handling, dependency integrity, or data-retention behavior.
This is a remote payload execution risk rather than confirmed embedded malicious code: the audited artifact does not itself contain an executable payload, but it directs the Agent to retrieve and execute one whose contents are outside the reviewed boundary.
Attack Path
- The user loads the reviewed Skill.
- The Agent follows the installation instruction and clones or installs code from the mutable GitHub repository.
- The repository owner, a compromised account, or a compromised dependency supplies code that differs from the reviewed documentation.
- The Agent configures the downloaded code with LLM and Feishu credentials and a Weibo authenticated session.
- The downloaded scripts execute with the Agent's local perm ...[truncated 832 chars]
- Remediation
View remediation
Remediation Suggestions
- Include every required script and configuration template in the audited package.
- If external retrieval is unavoidable, pin the source to an immutable commit and verify a cryptographic digest or trusted signature before execution.
- Require a new security review whenever the pinned source or dependencies change.
- Use dependency lockfiles with hashes and trusted package indexes.
- Display the exact source revision and requested permissions before installation.
- Run retrieved code in a sandbox with a read-only filesystem where possible, a minimal service account, and destination-restricted network access.
- Do not expose credentials until code integrity has been verified.
