T09 · Insecure Skill Coding Practices
- Location
scripts/teaming-manager.py:18- Finding
Plaintext Storage of Raw Personal Contact Information
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly coherent, but it persistently stores raw contact details and its helper script can expose complete personal records despite the skill promising masked contact output.
Review this skill before installing. It is not showing evidence of malware, but users should not enter real phone, email, QQ, or WeChat details unless they accept persistent local storage and possible raw-record exposure through the helper script. The publisher should add explicit consent, retention and deletion controls, restrictive file permissions, and ensure list/match outputs never include raw contact fields.
scripts/teaming-manager.py:18Plaintext Storage of Raw Personal Contact Information
scripts/teaming-manager.py:118Unauthenticated Enumeration and Disclosure of Complete Teaming Records
The declared behavior and the actual described operations do not fully align: the skill promises real-time competition calendar functionality while also persisting team requests and raw contact data locally. Behavior mismatches are dangerous because users and reviewers may not understand the real data handling, leading to unanticipated retention of sensitive information.
YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).
---
name: competition-assistant
description: 大学生竞赛助手 — 提供赛事月历生成与组队匹配服务。触发场景:(1) 用户询问比赛信息、赛事日程、近期竞赛、"汇总比赛"、"赛事月历"、"有哪些比赛"等;(2) 用户需要组队找队友、"匹配比赛队伍"、"找队友"、"帮我匹配"、描述组队需求如"我想找互联网+的队友"或"有没有人在做挑战杯缺人"。功能包括:实时获取教育部认可84项学科竞赛的报名时间、比赛时间;跨会话持久化的组队需求管理与智能匹配推荐。
---
# 大学生竞赛助手
我已经准�
The skill states that contact details will be stored across sessions, but it does not present a clear user warning, consent flow, retention policy, or sharing notice. Because the data is personally identifying and intended for later matching/disclosure, missing explicit informed consent materially raises privacy and compliance risk.
The skill describes capabilities that imply file read/write and network access, but it does not declare any explicit tool scope or permission boundaries. This increases the chance of over-broad execution in an agent runtime and makes it harder to audit or constrain what the skill is allowed to access.
The trigger phrases for team matching are broad enough to overlap with ordinary conversational requests, which can cause the skill to activate unexpectedly and begin collecting sensitive details like contact information. In this context, accidental activation is more dangerous because the skill performs cross-session persistence and later disclosure to other users.
The skill collects users' contact details, stores them persistently across sessions, and uses them for later matching and disclosure to other users. Even with masking on display, storing original contact values creates a sensitive data repository that could be exposed, misused, or retained longer than users expect.
This markdown file contains all user-facing instructions and schema descriptions in Chinese, and nowhere indicates that the skill is China-specific or that users may choose another language. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation.
The code stores user identifiers, names, free-time details, notes, and full contact information in a persistent file under the user's home directory without any visible consent, retention policy, or disclosure mechanism. For a cross-session matching tool, silent persistence of personal data raises privacy and compliance concerns and can surprise users who do not expect long-term storage.
The script persists full contact details in the request object and returns whole request records from list and match flows, so any caller of those functions can access unmasked personal contact data. In a team-matching assistant, this creates unnecessary exposure of sensitive personal information beyond the minimum needed for recommendation, increasing privacy and abuse risk.
This markdown file is entirely written in Chinese and provides no indication that users may choose another language or locale. Under the natural-language policy rule, a skill artifact that effectively enforces a specific language without opt-in can be considered a locale-policy violation.
The natural-language docstrings and CLI messages are written only in Chinese, with no indication that users may choose another language or locale. Under the policy, forcing a specific language without opt-in can be a natural-language policy violation unless clearly justified.
The manifest focuses on creating persistent teaming needs and recommending matches, but the code also implements mutation operations to change status and delete records. Those lifecycle-management capabilities may be reasonable implementation choices, but they are not described in the stated functionality.