T06 · System Persistence
- Location
SKILL.md:43- Finding
Mandatory Daily Cron Jobs Establish Cross-Session Persistence
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is not clearly malicious, but it asks agents to install and auto-update skills, create recurring cron jobs, and uses embedded folder tokens without enough scoping or safeguards.
Install only in an authorized environment after reviewing the referenced dependencies and cron jobs. Require pinned trusted skill versions, documented cron commands and removal steps, integrity checks for updates, and confirmation before overwriting _config. Treat the listed folder tokens as sensitive unless the service confirms they are only non-secret identifiers protected by separate authentication.
SKILL.md:43Mandatory Daily Cron Jobs Establish Cross-Session Persistence
SKILL.md:19Required Skill Dependencies Lack Version and Source Verification
SKILL.md:52Workspace Resource Tokens Are Embedded in a Distributable Skill
The skill description, title, and operational instructions are presented exclusively in Chinese, including the capability announcement instruction, without offering users a language or locale option. Under the stated policy, forcing a specific language without opt-in is a natural-language policy violation unless the locale restriction is clearly documented and justified.
The skill embeds shared folder tokens directly in the document and provides no handling guidance, sensitivity warning, or access-control caveat. Even if these are only identifiers, publishing resource tokens in broadly distributed onboarding content increases the chance of unauthorized discovery, misuse, or accidental disclosure of internal shared resources.
The skill directs the agent to create a local _config directory and maintain files, including an overwrite-style daily sync, without any explicit warning, confirmation step, or scope limitation. This can lead to unintended workspace modification or clobbering of existing files, especially because the cron task says to '覆盖更新' (overwrite update), making the behavior operationally risky even if not overtly malicious.
No suspicious patterns detected.