T09 · Insecure Skill Coding Practices
- Location
skills/smyx_common/scripts/util.py:296- Finding
Silent Registration Discloses API Keys or User Identifiers as Phone and Identity Data
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is framed as pet treadmill analysis, but it sends videos and identifiers to a broad cloud analysis/account system with under-disclosed token storage and account behavior.
Review before installing. Use only if you are comfortable sending pet videos, report history identifiers, and possibly username/phone-style open-id values to the Life Emergence cloud services. Avoid placing real API secrets in fields this skill may treat as identity, and do not use it in a shared workspace unless token storage and retention are acceptable.
skills/smyx_common/scripts/util.py:296Silent Registration Discloses API Keys or User Identifiers as Phone and Identity Data
skills/smyx_common/scripts/dao.py:58Authentication Tokens Are Stored in Plaintext in a Shared Workspace SQLite Database
skills/smyx_common/scripts/util.py:318Shared Request Utility Can Send Authentication Credentials to Arbitrary Absolute URLs
skills/smyx_common/requirements.txt:1Inconsistent Dependency Declarations Create Supply-Chain and Reproducibility Risk
Network communication, token/open-token management, phone-based login, local persistence, billing/recharge handling, and generic utilities are all outside the reasonable expectations for a pet treadmill exercise-analysis skill. In context, this broad hidden scope is dangerous because it crosses into authentication, account lifecycle, and monetization workflows while collecting user identifiers and uploaded media.
Network communication, token/open-token management, phone-based login, local persistence, billing/recharge handling, and generic utilities are all outside the reasonable expectations for a pet treadmill exercise-analysis skill. In context, this broad hidden scope is dangerous because it crosses into authentication, account lifecycle, and monetization workflows while collecting user identifiers and uploaded media.
Network communication, token/open-token management, phone-based login, local persistence, billing/recharge handling, and generic utilities are all outside the reasonable expectations for a pet treadmill exercise-analysis skill. In context, this broad hidden scope is dangerous because it crosses into authentication, account lifecycle, and monetization workflows while collecting user identifiers and uploaded media.
Network communication, token/open-token management, phone-based login, local persistence, billing/recharge handling, and generic utilities are all outside the reasonable expectations for a pet treadmill exercise-analysis skill. In context, this broad hidden scope is dangerous because it crosses into authentication, account lifecycle, and monetization workflows while collecting user identifiers and uploaded media.
Network communication, token/open-token management, phone-based login, local persistence, billing/recharge handling, and generic utilities are all outside the reasonable expectations for a pet treadmill exercise-analysis skill. In context, this broad hidden scope is dangerous because it crosses into authentication, account lifecycle, and monetization workflows while collecting user identifiers and uploaded media.
Network communication, token/open-token management, phone-based login, local persistence, billing/recharge handling, and generic utilities are all outside the reasonable expectations for a pet treadmill exercise-analysis skill. In context, this broad hidden scope is dangerous because it crosses into authentication, account lifecycle, and monetization workflows while collecting user identifiers and uploaded media.
Network communication, token/open-token management, phone-based login, local persistence, billing/recharge handling, and generic utilities are all outside the reasonable expectations for a pet treadmill exercise-analysis skill. In context, this broad hidden scope is dangerous because it crosses into authentication, account lifecycle, and monetization workflows while collecting user identifiers and uploaded media.
Network communication, token/open-token management, phone-based login, local persistence, billing/recharge handling, and generic utilities are all outside the reasonable expectations for a pet treadmill exercise-analysis skill. In context, this broad hidden scope is dangerous because it crosses into authentication, account lifecycle, and monetization workflows while collecting user identifiers and uploaded media.
Network communication, token/open-token management, phone-based login, local persistence, billing/recharge handling, and generic utilities are all outside the reasonable expectations for a pet treadmill exercise-analysis skill. In context, this broad hidden scope is dangerous because it crosses into authentication, account lifecycle, and monetization workflows while collecting user identifiers and uploaded media.
Network communication, token/open-token management, phone-based login, local persistence, billing/recharge handling, and generic utilities are all outside the reasonable expectations for a pet treadmill exercise-analysis skill. In context, this broad hidden scope is dangerous because it crosses into authentication, account lifecycle, and monetization workflows while collecting user identifiers and uploaded media.
Network communication, token/open-token management, phone-based login, local persistence, billing/recharge handling, and generic utilities are all outside the reasonable expectations for a pet treadmill exercise-analysis skill. In context, this broad hidden scope is dangerous because it crosses into authentication, account lifecycle, and monetization workflows while collecting user identifiers and uploaded media.
Network communication, token/open-token management, phone-based login, local persistence, billing/recharge handling, and generic utilities are all outside the reasonable expectations for a pet treadmill exercise-analysis skill. In context, this broad hidden scope is dangerous because it crosses into authentication, account lifecycle, and monetization workflows while collecting user identifiers and uploaded media.
The skill does not clearly warn users that videos, optional heart-rate data, and an identifier may be transmitted to cloud APIs for processing and history retrieval. In this context, the data is sensitive and potentially account-linked, so undisclosed external transmission substantially increases privacy and compliance risk.
Across the endpoint, request, and response descriptions, the referenced API appears to perform generic or human-health-oriented video analysis rather than pet exercise intensity assessment. In a skill that claims real-time pet rehabilitation and exercise guidance, this is dangerous because users may rely on outputs that are irrelevant, incorrect, or derived from an unintended analysis pipeline while sensitive video data is still transmitted off-device.
The documented response schema describes human face detection and constitution/organ diagnosis, which is fundamentally unrelated to the advertised pet treadmill intensity analysis use case. This mismatch strongly suggests the skill may send user-provided pet videos to an unrelated or repurposed backend, creating a serious integrity and privacy risk because consumers are misled about what data processing actually occurs.
The file implements generic user-account persistence unrelated to the stated pet treadmill intensity-analysis purpose, which is a strong scope mismatch. Unnecessary account-management code expands the attack surface, introduces storage of personal data, and may conceal capabilities not expected by users or reviewers.
The model stores authentication-style token and profile fields despite no clear need in a pet exercise analysis skill. Persisting tokens in a local SQLite database increases the risk of credential theft, account compromise, and privacy violations if the database file is exposed or improperly shared.
This utility silently performs external account creation/login, retrieves tokens, and persists them locally as part of generic request handling, even though that behavior is unrelated to pet treadmill intensity analysis. In the context of this skill, the code expands data access and identity scope far beyond what is needed, creating risk of unauthorized account provisioning, token misuse, and covert linkage of user identity to an unrelated backend service.
The skill declares no explicit tool scope even though its instructions require shell execution, filesystem access, environment/config reading, network/API access, and local file writes. That creates an over-privileged and weakly bounded execution model where an agent may invoke sensitive capabilities without clear least-privilege constraints or user-visible authorization boundaries.
The broad default trigger can cause the skill to activate automatically for any uploaded pet treadmill video that appears analysis-related. Overbroad activation is dangerous because it may initiate file handling, identifier collection, or cloud submission without sufficiently specific user intent or consent.
Automatic history-report listing and cloud query behavior exceed the core analysis function and can expose prior records and report links tied to a user identifier. In a health-adjacent context involving videos and optional heart-rate data, expanding into record retrieval materially raises confidentiality concerns.
Automatically saving uploaded files without a clear user-facing warning creates an avoidable privacy and retention risk. Users may believe uploads are used transiently for analysis, not persisted on disk where they may remain accessible after the session.
The skill explicitly instructs the agent to obtain an open-id from local config files or from the user before proceeding, expanding behavior into account/record access. Reading identifiers from local configuration is sensitive because it can exfiltrate or repurpose credentials/user IDs without clear user awareness, and linking analysis to cloud history increases privacy risk.
Requesting a username or phone number as open-id without a clear privacy warning or minimization rationale unnecessarily exposes personal identifiers. This is especially sensitive when combined with cloud-stored historical reports and uploaded video/biometric-adjacent data.
The manifest describes a skill for analyzing pet treadmill exercise intensity from video and optional heart-rate data. However, this service also implements add, edit, and delete operations for camera/device records, which are administrative data-management capabilities not described as part of the analysis function.