T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:73- Finding
Unverified Remote Installer Downloaded and Executed Directly
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly a coherent monitor-control guide, but it asks users to run an unverified remote installer and set persistent automation without enough safety guidance.
Review this skill before installing. Do not run the curl-to-bash Homebrew installer as written; use official Homebrew instructions or inspect and verify any installer first. Only create cron jobs if you want recurring display changes, and keep a note of how to list and remove them. Test monitor commands manually before binding them to shortcuts or scheduled jobs, especially factory reset, input switching, power, and color-gain changes.
SKILL.md:73Unverified Remote Installer Downloaded and Executed Directly
SKILL.md:171AppleScript Injection Through Unvalidated Brightness Argument
references/volume.md:26Predictable Shared Temporary File Used for Volume State
The skill’s invocation guidance is overly broad, telling the agent to use it whenever a user wants to control nearly any external display setting. Broad triggers can cause the skill to activate in contexts where shell commands, package installation, or automation setup were not explicitly requested, increasing the chance of unnecessary or unsafe operational guidance. In this skill’s context, that matters because later steps include package installation, scripting, and persistent automation changes.
The skill recommends executing a remote installation script fetched with curl and piped into a shell. This is dangerous because it runs code obtained over the network without local review, making the user dependent on the integrity of the remote source, transport, and repository state at execution time. In this skill, the risk is amplified because the command is presented as a convenience step during setup, which can normalize unsafe execution patterns.
> **Homebrew not installed?**
> ```bash
> /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
> ```
---
The skill explicitly instructs users to edit crontab, introducing session persistence through scheduled jobs. Persistence mechanisms can outlive the immediate task, continue making system changes unattended, and be difficult for less technical users to notice or reverse. Although the scheduled actions here are display-related rather than privilege-escalating, persistence still increases operational and security risk.
Use cron to switch display settings automatically at certain times:
crontab -e
Output size or generation rate is not bounded. Unbounded output enables denial-of-service through resource exhaustion, log flooding, or context-window stuffing.
0xD6)Turn the display panel on/off without cutting power to the device.
The skill instructs users to create cron-based display-setting changes but does not clearly warn that these jobs will continue running automatically until removed. Persistent automation can surprise users, affect future sessions, and make later troubleshooting harder, especially if settings change at fixed times without obvious attribution. The impact is limited because the actions are local display controls, but the persistence risk is real.
This markdown file includes shell scripts that write display luminance and RGB gain values, changing monitor state directly. Although persistence is mentioned later in the Tips section, the script section itself does not warn users before presenting commands that alter hardware settings and persist across power cycles.
The section instructs changing the display's on-screen display language to English as the example action. This is a natural-language locale preference imposed without offering alternatives or explaining that it should only be done at the user's request.
No suspicious patterns detected.