T08 · Insecure Dependencies
- Location
SKILL.md:190- Finding
Unpinned MobSDK Gradle Plugin Allows Unreviewed Supply-Chain Updates
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This appears to be a genuine MobLink Android integration helper, but it needs Review because it adds an unpinned Gradle build plugin and handles app secrets in plaintext project files.
Review before installing. Use only on a MobLink-specific Android project, pin the MobSDK Gradle plugin to a reviewed version, enable dependency verification or locking where possible, keep MobLink_Config.xlsx and any local credential files out of version control, avoid printing appSecret in logs or diffs, and delete the completed workbook after configuration is transferred. Treat any appSecret already committed or shipped in an APK as exposed and rotate it if needed.
SKILL.md:190Unpinned MobSDK Gradle Plugin Allows Unreviewed Supply-Chain Updates
SKILL.md:220MobTech Application Secret Is Collected and Embedded in Plaintext Project Files
The code is not an interactive guide or workflow assistant. Its primary function is to programmatically create a formatted Excel template file named 'MobLink_Config_Template.xlsx' containing fields and instructions related to MobLink integration. While the content domain matches MobLink Android integration, the behavior is materially different: it generates a document artifact on disk rather than guiding a user interactively. This is a meaningful description-behavior mismatch because the primary purpose and capability of the code are template generation and file output, which are not reflected in the declared description.
The README instructs the agent and user to handle sensitive values including appKey, appSecret, package/signing identifiers, privacy consent state, and a user-provided Excel configuration, but it does not include any guidance on secret handling, storage minimization, redaction, or safe disposal. In an agent-driven workflow, this omission can lead to credentials being copied into project files, logs, prompts, or generated artifacts, increasing the risk of accidental disclosure and privacy non-compliance.
The listed triggers include phrases like '我要在app中增加深度链接能力' and the guidance says to prioritize this skill whenever the question is related to Android deep links, scene restore, or compliance. These requests are broader than MobLink integration specifically and can overlap with many unrelated Android deep-link tasks, increasing the risk of unintended invocation.
The skill instructs users to place sensitive values such as appKey, appSecret, package identifiers, and signing metadata into an Excel workbook stored in the project directory, without warning about secrecy, access controls, or cleanup. This increases the chance that credentials are exposed through source control, backups, shared folders, or accidental disclosure during support workflows.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
["useMobCustomController", "是否使用 App 数据采集主动控制器:是/否", "否"],
["allowLocationData", "是否允许 MobLink 主动采集地理位置信息:是/否", "是"],
["allowDeviceIdData", "是否允许 MobLink 主动采集 OAID/Advertising ID/Android ID:是/否", "是"],
["allowAppListData", "是否允许 MobLink 主动采集应用列表信息:是/否", "是"],
["allowNetworkData", "是否允许 MobLink 主动采集 WIFI/基站/IP 等网络状态信息:是/否", "是"],
]
return create_sheet_with_header(wb, "隐私合规", headers, data)
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
["useMobCustomController", "是否使用 App 数据采集主动控制器:是/否", "否"],
["allowLocationData", "是否允许 MobLink 主动采集地理位置信息:是/否", "是"],
["allowDeviceIdData", "是否允许 MobLink 主动采集 OAID/Advertising ID/Android ID:是/否", "是"],
["allowAppListData", "是否允许 MobLink 主动采集应用列表信息:是/否", "是"],
["allowNetworkData", "是否允许 MobLink 主动采集 WIFI/基站/IP 等网络状态信息:是/否", "是"],
]
return create_sheet_with_header(wb, "隐私合规", headers, data)
The instructions, prompts, and trigger phrases are entirely in Chinese, which effectively imposes a specific language for user interaction. The file does not state that the skill is China-specific only, nor does it offer an opt-in or alternative language choice.
The document content is entirely Chinese-language and does not indicate that the skill is intended only for a Chinese-speaking or region-specific audience, nor does it offer an alternative language option. Under the policy, forcing a specific language without user opt-in is a natural-language locale violation.