T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:78- Finding
Unpinned Remote Installation Script Is Executed Directly by a Shell
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill mostly matches its event-management purpose, but it needs Review because it requires opaque telemetry with app identifiers and offers an unsafe curl-to-shell installer.
Prefer the npm install path, do not run the curl-to-shell installer unless you have independently reviewed and trust it, and treat appkey/dataSourceId values as sensitive tenant identifiers. Before using write operations, require explicit confirmation because created event definitions are documented as irreversible.
SKILL.md:78Unpinned Remote Installation Script Is Executed Directly by a Shell
SKILL.md:32Mandatory Telemetry Sends Skill Usage and User-Supplied Application Identifiers
Using curl ... | sh is a classic command-chaining anti-pattern because it executes remote content immediately with no review or integrity check. In an agent context, this is more dangerous because an automated system may follow the instruction non-interactively, turning documentation into a direct arbitrary-code-execution path.
npm install -g @umengfe/umeng-cli
curl -fsSL https://raw.githubusercontent.com/umeng/umeng-cli/main/scripts/install.sh | sh
安装完成后再次运行 `umeng-cli --version` 验证。
The skill instructs the agent to perform telemetry trace calls that are not required to fulfill the user's primary event-management task. This creates an unnecessary outbound data flow and expands the action surface by causing the agent to send metadata to another command path without explicit user benefit or consent.
The skill explicitly tells the agent to send the user's appkey/dataSourceId in a telemetry event before the business API call, but it does not require a clear privacy notice or consent from the user. Appkeys may be sensitive operational identifiers, and transmitting them for tracking purposes can violate least-privilege and data-minimization expectations.
This instruction causes the agent to exfiltrate a user-supplied AppKey to telemetry prior to performing the requested task. Even if the endpoint is controlled by the same vendor, this is still a separate reporting action unrelated to core task completion and can expose tenant/application identifiers unnecessarily.
The skill recommends installation via a fetched remote shell script from GitHub, which asks the user or agent to trust code at execution time without integrity verification. If the remote content, repository, transport assumptions, or upstream account are compromised, arbitrary code could run on the host.
npm install -g @umengfe/umeng-cli
curl -fsSL https://raw.githubusercontent.com/umeng/umeng-cli/main/scripts/install.sh | sh
安装完成后再次运行 `umeng-cli --version` 验证。