T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:16- Finding
Unverified Remote Installer Scripts Are Executed Directly
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 16–17
Vulnerability Type: Remote payload retrieval and execution
Risk Level: Criticalmarkdown - **macOS / Linux**: `curl -fsSL https://d.officecli.ai/install.sh | bash` - **Windows (PowerShell)**: `irm https://d.officecli.ai/install.ps1 | iex`Technical Analysis
The setup instructions download mutable scripts from
d.officecli.aiand immediately execute them using Bash or PowerShell. The commands do not pin an immutable installer version, verify a checksum or cryptographic signature, or provide an inspection step before execution.HTTPS protects the connection in transit but does not protect users if the hosting server, domain, publishing account, TLS endpoint, or installer deployment process is compromised. Because the effective executable payload remains external to the reviewed Skill, it can change after this package has passed an audit.
Installing
officecliis relevant to the Skill's declared document-generation function. However, executing an unaudited remote response is not the least-risk installation method, particularly because the file also identifies a release-download alternative. The issue affects both supported installation paths:- On macOS and Linux,
curlsends the response body directly tobash. - On Windows,
Invoke-RestMethodretrieves the response andInvoke-Expressionevaluates it as PowerShell code.
No subsequent credential theft, persistence, destructive operation, or privilege-escalation command was found in the audited file. Nevertheless, these commands create an unrestricted code-execution channel through which such behavior could be delivered later.
Attack Path
- An agent or user loads the Skill and finds that
officecliis unavailable. - The agent or user follows one of the documented setup commands.
- An attacker compromises the installer host, domain, TLS termination point, deployment creden ...[truncated 1292 chars]
- On macOS and Linux,
- Remediation
View remediation
Remediation Suggestions
- Remove the direct
curl | bashandirm | iexinstallation instructions. - Direct users to a version-pinned release hosted on the identified official GitHub releases page.
- Publish SHA-256 or stronger checksums through an independently protected channel and require verification before execution.
- Prefer cryptographically signed binaries or packages and verify the publisher signature and expected signing identity.
- If installer scripts must remain available:
- Download the script to a local file rather than piping it into an interpreter.
- Use a versioned, immutable URL.
- Verify its checksum or signature.
- Display or inspect it before execution.
- Execute it without administrative privileges unless a documented operation strictly requires elevation.
- Document the files, network destinations, PATH changes, and other system modifications performed by the installer.
- Provide platform-native, version-pinned package-manager instructions where package authenticity and integrity verification are supported.
- In automated agent workflows, require explicit user approval before installing software or running any downloaded executable content.
- Remove the direct
