T06 · System Persistence
- Location
README.md:98- Finding
Optional Login Persistence Through LaunchAgent Registration
- Content
View full analysis
~/Library/LaunchAgents/com.openclaw.face.plist launchctl load ~/Library/LaunchAgents/com.openclaw.face.plist # Uninstall launchctl unload ~/Library/LaunchAgents/com.openclaw.face.plist rm ~/Library/LaunchAgents/com.openclaw.face.plist ``` ### Technical Analysis The documentation instructs users to place a property-list file in the per-user `~/Library/LaunchAgents` directory and load it through `launchctl`. A loaded LaunchAgent can execute its configured program automatically across login sessions. Persistent execution is not required for the Skill's core on-demand desktop status-monitoring functionality. The mechanism is presented as an optional auto-start feature and removal instructions are provided, but it still expands execution from an explicitly initiated run to automatic cross-session execution. The referenced `com.openclaw.face.plist` is absent from the audited artifact. Consequently, the installation command cannot create a functional service from this package as delivered: `sed` will fail to read the missing source file and may leave an empty destination file. The actual command, arguments, environment, and restart policy that would be registered therefore could not be reviewed. ### Attack Path 1. A user obtains or is later provided the referenced plist file. 2. The user follows the documented auto-start instructions. 3. The plist is copied into `~/Library/LaunchAgents`. 4. `launchctl load` registers and starts the configured process. 5. The configured executable continues to run automatically after future logins. 6. If the plist or referenced executable is subsequently replaced or compromised, attacker-controlled code can execute each time the us ...[truncated 521 chars]- Remediation
View remediation
