Security audit
Security checks for vulnerabilities and agentic risk
The skill mostly performs disclosed cloud-based image analysis, but it silently creates/reuses a remote identity and stores tokens locally while also carrying copied pet-health/generic-analysis code and docs that do not cleanly match the plant-analysis purpose.
Review before installing. This skill sends plant images/videos or URLs to an external LifeEmergence service, can query cloud report history, and silently creates/reuses an internal account identity while storing tokens in the workspace data directory. Install only if you accept that account-linked cloud workflow and the copied pet-health/generic-analysis remnants do not create ambiguity for your use case.
The strongest concern is that the skill appears to manage identity resolution, token/account creation, workspace files, and remote HTTP communication while lacking the promised transpiration-analysis logic. In context, that means a benign-seeming plant skill could actually collect local files, link activity to internal identities, and transmit data to backend services without clear user awareness.
The strongest concern is that the skill appears to manage identity resolution, token/account creation, workspace files, and remote HTTP communication while lacking the promised transpiration-analysis logic. In context, that means a benign-seeming plant skill could actually collect local files, link activity to internal identities, and transmit data to backend services without clear user awareness.
The strongest concern is that the skill appears to manage identity resolution, token/account creation, workspace files, and remote HTTP communication while lacking the promised transpiration-analysis logic. In context, that means a benign-seeming plant skill could actually collect local files, link activity to internal identities, and transmit data to backend services without clear user awareness.
The strongest concern is that the skill appears to manage identity resolution, token/account creation, workspace files, and remote HTTP communication while lacking the promised transpiration-analysis logic. In context, that means a benign-seeming plant skill could actually collect local files, link activity to internal identities, and transmit data to backend services without clear user awareness.
The strongest concern is that the skill appears to manage identity resolution, token/account creation, workspace files, and remote HTTP communication while lacking the promised transpiration-analysis logic. In context, that means a benign-seeming plant skill could actually collect local files, link activity to internal identities, and transmit data to backend services without clear user awareness.
The strongest concern is that the skill appears to manage identity resolution, token/account creation, workspace files, and remote HTTP communication while lacking the promised transpiration-analysis logic. In context, that means a benign-seeming plant skill could actually collect local files, link activity to internal identities, and transmit data to backend services without clear user awareness.
The strongest concern is that the skill appears to manage identity resolution, token/account creation, workspace files, and remote HTTP communication while lacking the promised transpiration-analysis logic. In context, that means a benign-seeming plant skill could actually collect local files, link activity to internal identities, and transmit data to backend services without clear user awareness.
The strongest concern is that the skill appears to manage identity resolution, token/account creation, workspace files, and remote HTTP communication while lacking the promised transpiration-analysis logic. In context, that means a benign-seeming plant skill could actually collect local files, link activity to internal identities, and transmit data to backend services without clear user awareness.
The strongest concern is that the skill appears to manage identity resolution, token/account creation, workspace files, and remote HTTP communication while lacking the promised transpiration-analysis logic. In context, that means a benign-seeming plant skill could actually collect local files, link activity to internal identities, and transmit data to backend services without clear user awareness.
The strongest concern is that the skill appears to manage identity resolution, token/account creation, workspace files, and remote HTTP communication while lacking the promised transpiration-analysis logic. In context, that means a benign-seeming plant skill could actually collect local files, link activity to internal identities, and transmit data to backend services without clear user awareness.
The strongest concern is that the skill appears to manage identity resolution, token/account creation, workspace files, and remote HTTP communication while lacking the promised transpiration-analysis logic. In context, that means a benign-seeming plant skill could actually collect local files, link activity to internal identities, and transmit data to backend services without clear user awareness.
The strongest concern is that the skill appears to manage identity resolution, token/account creation, workspace files, and remote HTTP communication while lacking the promised transpiration-analysis logic. In context, that means a benign-seeming plant skill could actually collect local files, link activity to internal identities, and transmit data to backend services without clear user awareness.
The strongest concern is that the skill appears to manage identity resolution, token/account creation, workspace files, and remote HTTP communication while lacking the promised transpiration-analysis logic. In context, that means a benign-seeming plant skill could actually collect local files, link activity to internal identities, and transmit data to backend services without clear user awareness.
The strongest concern is that the skill appears to manage identity resolution, token/account creation, workspace files, and remote HTTP communication while lacking the promised transpiration-analysis logic. In context, that means a benign-seeming plant skill could actually collect local files, link activity to internal identities, and transmit data to backend services without clear user awareness.
YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).
---
name: "smyx-transpiration-rate-estimation-analysis"
description: "AI-powered transpiration rate estimation for indoor plants. From smart planters or fixed cameras, uses thermal infrared images of leaves (preferred) — or regular RGB images combined with ambient temperature/humidity — to estimate the leaf-to-air temperature difference, combines radiation/humidity parameters (sensor or model-inferred), and computes a relative transpiration rate index (0-100%). Transpiration rate correlates with root water-uptake activity, indirectly reflecting root health and water transport capacity. Helps determine whether the plant is water-stressed, has da
The documented API endpoints and scenario code are for pet health analysis, which materially contradicts the stated purpose of this skill: plant transpiration estimation. This kind of cross-domain mismatch is dangerous because an agent integrating the skill could call unrelated production endpoints, expose or retrieve the wrong dataset, or operate on sensitive health-report functionality under a misleading plant-analysis label.
The script for plant transpiration analysis exposes unrelated pet-oriented parameters and list functionality, including pet_type, pet-health help text, and a listing path keyed by internal user identity. This kind of cross-domain code reuse can cause the wrong backend functionality or data domain to be invoked, increasing the risk of unauthorized access to unrelated analysis records or accidental processing of the wrong tenant/data scope.
The file claims to implement plant transpiration-rate estimation, but the code actually exposes a generic video analysis and history-retrieval CLI. This mismatch is dangerous because operators may grant permissions, provide data, or trust outputs under false assumptions, enabling deceptive data processing and misuse of the skill in workflows that expect narrow plant-analysis behavior.
This code creates or reuses synthetic open-id style identities, reads identity material from workspace files, and persists user identifiers locally without a clear relationship to transpiration analysis. For a plant-care skill, covert identity creation and persistence are unjustified and increase the risk of tracking, impersonation, and hidden coupling to external backend services.
The utility layer performs remote account provisioning, token acquisition, token caching, and authenticated API request handling that are unrelated to plant transpiration estimation. In the context of a plant-analysis skill, this is dangerous because it silently expands capability into identity management and external service access, enabling undisclosed data transmission and persistent authentication state.
The code silently calls /sys/phoneLogin with register=1 and silent=1 to create or log into a remote account using a locally derived username. That is a strong capability mismatch for a plant transpiration skill and is dangerous because it can provision remote identities and transmit identifiers to external infrastructure without meaningful user awareness.
The skill instructs execution of local Python scripts, file saving, network access, and shell-like commands, but the manifest does not declare any explicit tool scope or allowed-tools boundary. This increases the chance that an agent will grant broader capabilities than users expect, making filesystem, environment, and network actions less transparent and harder to constrain.
Cloud history retrieval and report-link generation are secondary data-access features not justified by the core purpose of estimating transpiration from imagery. They expand the skill from analysis into record browsing, which can expose historical user data and enable report enumeration if access controls are weak.
A broad trigger phrase for history-report retrieval can cause the skill to invoke cloud listing behavior during ordinary conversation, leading to unintended data access or disclosure. Although this is more of a safety and privacy design flaw than an exploit primitive, it still widens the chance of accidental backend operations.
The skill states that uploaded attachments are automatically saved locally, but the description does not provide a clear upfront warning to the user. Silent local persistence of user files creates privacy and retention risks, especially when the skill is presented as a simple analysis tool.