T09 · Insecure Skill Coding Practices
- Location
scripts/zoodata.py:62- Finding
Bearer Credential Can Be Transmitted over Plaintext HTTP or to an Overly Broad Host Set
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill mostly does what it says, but it handles a paid API key with overly broad endpoint trust and a mutable install path that users should review before installing.
Review before installing. Pin the repository or release you install, avoid using ZOODATA_BASE_URL unless you fully trust the destination, and do not set it to HTTP or localhost with a production API key. Expect ZooData API calls to consume credits and confirm broad scans before running them.
scripts/zoodata.py:62Bearer Credential Can Be Transmitted over Plaintext HTTP or to an Overly Broad Host Set
README.md:17Installation Uses an Unpinned npm Launcher and Mutable Remote Repository
A second description-behavior mismatch is present: the skill claims to use a defined opportunity-scanning flow, but the referenced tooling exposes broader keyword, competitor, review, and diagnostic capabilities. In context, this matters because the skill also handles an API key and local credential sources, so under-scoped descriptions can conceal a materially larger attack surface.
A second description-behavior mismatch is present: the skill claims to use a defined opportunity-scanning flow, but the referenced tooling exposes broader keyword, competitor, review, and diagnostic capabilities. In context, this matters because the skill also handles an API key and local credential sources, so under-scoped descriptions can conceal a materially larger attack surface.
The manifest describes a skill for discovering what to sell via category scanning, candidate validation, and ranking, but this file implements a broad ZooData CLI surface including market-entry analysis, competitor war-room analysis, pricing analysis, daily monitoring, listing audits, review deep-dives, raw review export, and keyword intelligence workflows. Those operations go well beyond a ranked opportunity scanner and materially expand what the bundled code can do.
The manifest positions this skill as a niche/product opportunity finder for users without a target product, but these workflows accept my_asin, perform deep competitor analysis, pricing benchmarking, brand drill-down, and market benchmarks for existing products. Those are post-selection evaluation capabilities rather than discovery capabilities.
The manifest says to use another skill for tracking category trends over time, yet this file implements daily-radar for unattended daily monitoring of tracked ASINs with historical comparison, competitor detection, and review pulse. Persistent monitoring of known products is not justified by a discovery scanner whose purpose is to find new opportunities.
The manifest explicitly says this skill should be used to discover what to sell when the user has no specific target yet, and says evaluating a niche already named should use amazon-market-entry-analyzer instead. The listing-audit workflow accepts --my-asin and performs a benchmark audit of a specific product listing, which is a separate evaluation/audit capability not justified by the discovery-only purpose.
The installation command uses npx skills add SerendipityOneInc/ZooData-Skills without pinning a specific package or skill version, so users may fetch whatever version is current at execution time. That creates a supply-chain risk: if the upstream package, dependency chain, or referenced skill content is changed or compromised, users could install and run unexpected code or prompts.
The skill advertises access to powerful capabilities (environment secrets, file reads, network, and shell) but does not declare an explicit tool/permission scope in the manifest. That weakens least-privilege controls and makes it easier for the skill to invoke sensitive operations beyond its stated purpose, especially since the document references a shared CLI, local config reads, temporary file handling, and network access.
The invocation phrases are broad enough that the skill may be selected for ordinary shopping or brainstorming requests that only loosely mention product ideas or what to sell. Unintended activation is risky here because the skill can consume paid API credits, access a secret API key, and trigger multi-call scans with network activity that the user may not have intended.
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 mentions validating opportunities with brand analysis and price structure, but this file also ships a prompt-as-data review-analysis toolkit that fetches raw reviews, renders prompts for an external LLM workflow, and aggregates labeled outputs. That is a specialized review-intelligence subsystem and not an obvious requirement for a product opportunity discoverer as described.
The review-tagging prompt explicitly instructs the caller's LLM that output must be in English and to translate non-English text before extracting. This is a natural-language locale policy constraint applied unconditionally, with no user choice or documented region-specific justification.
The example prompt "Run a quick scan and show me what opportunities are out there" is broad and lacks domain-specific constraints, making it resemble common conversational requests rather than a narrowly scoped skill trigger. The README does not provide explicit exclusion conditions or clarify when such a request should or should not invoke this skill.
The instructions require responses to be in the user's language and state that output language must match the user's input language. This is a natural-language locale policy constraint with no explicit user choice or opt-in mechanism documented.
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_")
No suspicious patterns detected.