T08 · Insecure Dependencies
- Location
README.md:19- Finding
Unpinned Package Execution During Installation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This appears to be a real Amazon research skill, but it needs review because its API key handling and bundled workflow documentation are broader than a typical scoped analysis skill.
Review before installing. Use this only if you are comfortable giving it a ZooData API key and spending ZooData credits for Amazon research. Prefer setting ZOODATA_API_KEY only in a controlled environment, do not set ZOODATA_BASE_URL to localhost with a production key, and treat review-derived insights as potentially affected by hostile review text. Pin or verify the installer command before use.
README.md:19Unpinned Package Execution During Installation
scripts/zoodata.py:63Production API Credential Can Be Transmitted to a Localhost Service
scripts/zoodata.py:910Externally Controlled Review Text Is Embedded Directly into an Agent Prompt
The skill description materially understates its behavior: beyond general Amazon analysis, it performs specialized workflows, accesses additional credential locations, and exposes a broader command surface including review export and LLM-assisted processing. This mismatch is dangerous because trust and approval decisions may be made on incomplete information, leading operators to authorize data access, local file reads, or network actions they did not realize the skill could perform.
Referenced artifact was not completely inspected
> **Modes are CLI-local presets, NOT API parameters.** `zoodata.py` expands `--mode` into real filter fields before the call — copy them from `PRODUCT_MODES` in
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
The skill advertises executable behavior involving environment access, file reads, network access, and shell execution, but it does not declare an explicit tool scope such as permissions or allowed-tools. That weakens policy enforcement and reviewability: a host agent may grant broader capabilities than intended, and users or platform operators cannot clearly verify the minimum privileges required.
The guide explicitly instructs the agent to never expose error details to users, which can suppress relevant transparency about failures, degraded results, or inability to validate outputs. In this skill, that matters because the agent is performing multi-step market analysis and may silently substitute estimates or alternate paths, causing users to trust conclusions without knowing important reliability limits.
The trigger list for composite product recommendations is broad and includes generic phrases like 'help me choose' and 'most suitable for me', which can cause the skill to activate for loosely related requests. In an agent environment, this can route users into Amazon-specific workflows unexpectedly, increasing the chance of irrelevant tool use, unnecessary data collection, or confusion about the assistant’s scope.
The seller-origin case study trigger includes a broad activation phrase ('sellers from a specific country') that may match general questions about merchants or nationality outside the intended Amazon competitor-analysis context. Although the section includes good safeguards against inferring origin, unintended invocation could still steer the agent into sensitive nationality-based analysis when the user did not clearly request Amazon-specific market research.
The trigger phrase "what do users want" is overly generic and can match many ordinary requests outside the intended Amazon category-consumer-insights workflow. In an agentic skill-routing context, this can cause accidental activation, leading the system to invoke broad analysis behavior or external data queries when the user did not clearly request this capability.
The manifest describes a general analysis and research engine for broad Amazon exploration, but this file is dedicated to generating and optimizing listing copy, backend search terms, and content rewrites. That is a materially different user-facing function from analysis/reporting and expands the skill into content creation rather than just research.
The trigger phrase set for competitor listing analysis is broad enough to match ordinary user language without clearly constraining intent or task boundaries. In an agent routing context, this can cause the wrong skill to activate, leading to unintended access to external data tools or execution of workflows the user did not explicitly request.
Phrases like 'write listing' or 'help me write product page' are vague everyday requests that can overlap with many non-Amazon content tasks. In a multi-skill system, ambiguous activation increases the risk of misrouting, causing this skill to inappropriately engage external research steps, consume privileged API access, or generate domain-specific output when another safer skill should handle the request.
The diagnosis triggers use broad language such as 'what's wrong with my listing' and 'improve my listing,' which can capture unrelated requests and route them into a tool-using Amazon workflow. Because this skill interfaces with an external script and API-backed analysis, accidental activation expands the attack surface and may lead to unnecessary data processing or user-confusing actions.
The skill text explicitly says to load for broad market monitoring, competitor tracking, or anomaly detection, which creates an overbroad trigger surface for a powerful analysis skill. In an agentic system, vague activation criteria can cause the skill to be invoked for loosely related requests, increasing the chance of unnecessary external data access, unintended task expansion, or policy-bypassing use in contexts where a more constrained skill should have been selected.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# ─── Configuration ───────────────────────────────────────────────────────────
DEFAULT_BASE_URL = "https://api.zoodata.ai/openapi/v2"
API_BASE_PATH = "/openapi/v2"
KEYWORD_DATE_RANGE_MAX_DAYS = 93
KEYWORD_TIMELINE_MAX_DAYS = 61
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# ─── Configuration ───────────────────────────────────────────────────────────
DEFAULT_BASE_URL = "https://api.zoodata.ai/openapi/v2"
API_BASE_PATH = "/openapi/v2"
KEYWORD_DATE_RANGE_MAX_DAYS = 93
KEYWORD_TIMELINE_MAX_DAYS = 61
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# ─── Configuration ───────────────────────────────────────────────────────────
DEFAULT_BASE_URL = "https://api.zoodata.ai/openapi/v2"
API_BASE_PATH = "/openapi/v2"
KEYWORD_DATE_RANGE_MAX_DAYS = 93
KEYWORD_TIMELINE_MAX_DAYS = 61
The manifest describes a broad Amazon research/analysis skill, but this shared script also exposes a distinct prompt-as-data toolkit for raw review extraction, prompt rendering, and local aggregation intended to drive another LLM workflow. Those commands are not merely implementation details of API access; they add a separate review-processing surface that goes beyond the manifest's stated role as a general analysis engine.
This code includes a natural-language instruction that the review-tagging output 'must be in English' and to translate non-English text before extracting. That imposes a specific language policy on all uses of the skill without offering a user choice or documenting a justified locale constraint.
The manifest positions this skill as a general Amazon-domain analysis and multi-endpoint research engine for broad or composite requests, but the script also contains specialized workflows such as market-entry, competitor-analysis, pricing-analysis, daily-radar, listing-audit, opportunity-scan, and review-deepdive. These are narrower expert playbooks with opinionated business logic, not obviously required to satisfy the stated general-purpose overview/research role.
The example prompt "Analyze the yoga mat market on Amazon" is a natural-language invocation without any explicit trigger syntax, boundary, or exclusion conditions. In a manifest/README context, this can make activation scope feel broad because similar everyday requests could unintentionally map to the skill.
The cross-validation section uses vague trigger phrases such as 'full picture' and 'cross-validate', which are common in many domains and could invoke this Amazon-analysis skill when the user intended a different type of research. The main risk is misrouting and over-broad tool execution across multiple endpoints rather than direct security compromise.
Dynamic getattr() with a non-literal attribute name can access arbitrary object attributes, potentially bypassing access controls.
"priceMin", "priceMax", "ratingMin", "ratingMax", "bsrMin", "bsrMax",
"salesGrowthRateMin", "salesGrowthRateMax", "sellerCountMin", "sellerCountMax",
"variantCountMin", "variantCountMax"):
val = getattr(args, attr.replace("Min", "_min").replace("Max", "_max")
.replace("monthly", "monthly_").replace("review", "review_")
.replace("sales", "sales_").replace("Growth", "_growth_")
.replace("Rate", "rate_").replace("price", "price_")
The check command verifies credential configuration and can actively probe multiple API endpoints, including optional paid endpoint tests. That operational diagnostics surface is useful for maintenance, but it is not part of the manifest's described user-facing purpose of Amazon market/product research and analysis.