T06 · System Persistence
- Location
references/README.md:50- Finding
Privileged Cross-Session Persistence Through Windows Task Scheduler and WSL Root
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill appears intended to install Hermes on Windows, but it relies on unaudited scripts, automatic updates, and persistent high-privilege startup behavior.
Install only if you trust the publisher and can inspect the missing PowerShell scripts from an official source. Before running it, verify what GitHub repositories and release artifacts it downloads, avoid highest-privilege auto-start unless necessary, and be prepared to remove the scheduled task and WSL files during uninstall.
references/README.md:50Privileged Cross-Session Persistence Through Windows Task Scheduler and WSL Root
references/README.md:85Unverified Remote Payload Download and Automatic Execution
The skill advertises one-click installation, background persistence, auto-start, and auto-update behavior without clearly warning users that it will modify startup behavior and keep services running in the background. In a Windows/WSL deployment context, undocumented persistence increases the risk of users authorizing lasting system changes they did not fully understand, which is a meaningful security and consent issue even though the markdown itself is not executing code.
The entire skill documentation is written in Chinese and does not indicate that the language is optional, selectable, or justified by a region-specific requirement. This can constitute a locale/language policy issue when a skill implicitly forces a specific language without user opt-in.
No suspicious patterns detected.