T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:3- Finding
Unattended High-Privilege Remote Control Without Adequate Authorization Gates
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill openly enables full unattended remote control of paired devices, but its camera, screen, notification, location, shell, file, app, and process controls are too powerful for the limited consent and scoping guidance provided.
Only install this for devices you own or are formally authorized to administer. Before use, require explicit consent and visible approval for screen, camera, notifications, location, shell, file transfer, app install/uninstall, process kill, and service or registry changes. Avoid using it for covert monitoring, credential access, or broad file browsing, and ensure gateway access is strongly authenticated and auditable.
SKILL.md:3Unattended High-Privilege Remote Control Without Adequate Authorization Gates
The skill exposes highly sensitive capabilities—unattended remote control, screen recording, camera access, notification reading, GPS, file manipulation, and shell execution—without prominent warnings, consent requirements, or abuse-prevention constraints. In this context, the absence of clear privacy and integrity safeguards makes misuse substantially more dangerous because the skill is purpose-built for covert device access and control.
The activation description is extremely broad and explicitly includes unattended remote control, screen/camera capture, shell execution, app installation, and 'device ghosting'. That makes it easy for the agent to invoke this skill for loosely related remote-access or monitoring prompts without strong scoping or consent checks, increasing the chance of unauthorized surveillance or takeover.
This reference documents process-termination commands such as Stop-Process and forceful PID kills in a skill explicitly designed for unattended remote control of devices. In that context, destructive commands can be executed on a remote node without local user awareness, causing loss of unsaved work, disruption of security tools, or service instability; the absence of warnings or guardrails materially increases misuse risk.
The file operation examples include writing, appending, deleting, and copying files on remote systems with no warning about user-data destruction, overwrite risk, or sensitive file access. Because this skill enables full unattended remote management, these examples can directly facilitate tampering with evidence, persistence artifacts, configuration, or personal data on paired devices.
Silent install and uninstall commands are especially risky in a remote-takeover skill because they enable software changes without user interaction or visibility. That can be abused to deploy unwanted tooling, remove protections, or alter a device state covertly; documenting this without warnings normalizes stealthy system modification.
Registry modification examples can create persistent configuration changes and are commonly used for autostart, policy alteration, or disabling protections. In an unattended remote-control context, presenting write operations without warnings significantly raises the chance of persistence abuse or long-lived system tampering.
Android install/uninstall plus screenshot and screen-recording commands are highly sensitive because they affect both device integrity and user privacy. Within a skill whose stated purpose is unattended remote takeover, these examples enable covert app deployment and direct capture of potentially confidential on-screen content without any privacy or consent warning.
Linux examples for kill -9 and systemctl restart can abruptly terminate applications or critical services, potentially causing outages, corruption, or disabling monitoring/security functions. In the context of remote device control, such commands become more dangerous because they can be issued at scale or without the device user's knowledge.
macOS screenshot capture and forced app quit examples implicate both privacy and availability: screenshots may expose sensitive user data, and quitting apps can discard unsaved work. Because the skill is for unattended takeover, omission of privacy and data-loss warnings materially increases the risk of covert surveillance and user harm.