T08 · Insecure Dependencies
- Location
SKILL.md:34- Finding
Unpinned Third-Party SDK Dependency Creates Supply-Chain Risk
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill appears to perform its stated Tencent Cloud face-liveness check, but it handles sensitive face images with under-disclosed remote processing and logs full image URLs.
Review before installing. Use only with images you are allowed to process through Tencent Cloud, prefer tightly scoped Tencent Cloud credentials, avoid long-lived or sensitive signed image URLs, and run it in an environment where stderr logs are not broadly retained or shared.
SKILL.md:34Unpinned Third-Party SDK Dependency Creates Supply-Chain Risk
scripts/main.py:216Sensitive Image URL Is Logged to Standard Error Without Redaction
The skill declares use of environment-based secrets (TENCENTCLOUD_SECRET_ID and TENCENTCLOUD_SECRET_KEY) but does not declare any explicit tool scope, permissions, or allowed-tools boundary. This creates an authorization transparency gap: an agent or reviewer cannot easily tell that the skill needs secret access, increasing the risk of unintended secret exposure or overbroad execution in a larger agent framework.
This skill handles face images and image URLs, which are biometric and highly sensitive personal data, yet it does not warn users that their data will be transmitted to Tencent Cloud for remote processing. Without clear disclosure and consent language, users may unknowingly send sensitive biometric data to a third party, creating privacy, compliance, and trust risks that are especially serious given the data type.
The script transmits biometric data (face images) or user-supplied image URLs to Tencent Cloud for processing, but it does not present an explicit privacy notice, consent check, or clear warning at the point of transmission. Because facial images are sensitive personal data, silent upload can violate user expectations, internal policy, or privacy/legal requirements, especially when the skill is invoked by another agent on a user's behalf.
All user-facing documentation is written in Chinese and the skill does not indicate whether another language is supported or whether Chinese is required for a region-specific reason. Under the language/locale policy, forcing a specific language without user opt-in can be a natural-language policy violation unless the constraint is clearly justified.