T06 · System Persistence
- Location
SKILL.md:139- Finding
Persistent Repository Reporting to a Hard-Coded DingTalk Recipient
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill clearly performs Git daily reporting, but it creates a persistent daily job that sends repository activity and review findings to a fixed DingTalk recipient without user-selected scoping or confirmation.
Review carefully before installing. Only use this skill if the listed repositories and DingTalk target are truly yours, and require a sanitized preview, redaction of secret findings, and an explicit way to list and remove the scheduled job before enabling daily delivery.
SKILL.md:139Persistent Repository Reporting to a Hard-Coded DingTalk Recipient
SKILL.md:55Secret Scanner Can Copy Credential Values into Externally Delivered Reports
SKILL.md:55Unsafe Parsing of Git Filenames Allows Option Injection and Incorrect File Scanning
The skill sets up unattended scheduled delivery of commit metadata, changed-file details, and code-review findings to a DingTalk target without an explicit consent/confirmation step that clearly warns about ongoing external transmission. In this context, repository activity, filenames, branch names, and review findings can reveal sensitive internal project structure or secrets-related indicators, making silent recurring exfiltration to a chat target a real privacy/security risk.
The file consistently instructs the skill to operate and respond in Chinese, including report templates, examples, and the scheduled payload text. There is no indication that the user can choose another language or that the Chinese-only behavior is a justified locale-specific constraint.
The manifest and surrounding documentation repeatedly specify that voc-frontend and voc-backend should report only the dev branch. The example message content instead labels both voc projects as origin/main, which conflicts with the intended behavior and could mislead an implementing agent.
The skill documentation consistently states that image-tool covers all remote branches while voc-frontend and voc-backend cover only origin/dev. However, the sample AI reply says it will send reports for 'image-tool 和 voc 项目所有 remote 分支', which directly contradicts the declared branch scope for voc projects.