T08 · Insecure Dependencies
- Location
SKILL.md:19- Finding
Unreviewable External Executable Dependency Handling Sensitive Credentials
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 19-21 and 28-33
Vulnerability Type: Unpinned and unauditable third-party executable dependency
Risk Level: HighVulnerable Code Snippet
markdown 2. runs `orchestrate.py <job> --draft` — uploads photos to eBay, auto-picks the category, writes the title/description, infers item specifics, and runs eBay's own validator,markdown This skill wraps the ListBlitz pipeline (not bundled — get it at the link below and place it in your workspace as `listblitz/`). Configure `config.env` per its SETUP.md (eBay developer keyset, Anthropic key). Full kit — standalone Telegram bot, per-category specifics inference, docs and support: **https://jenkinsscotty.gumroad.com/l/zmtxiu**Technical Analysis
The skill's core
orchestrate.pyimplementation is not included in the audited project. Users are instructed to acquire it from an external commercial download page and execute it locally. The instructions provide no immutable version, cryptographic checksum, digital signature, reproducible build information, or source repository through which the downloaded implementation can be independently verified.This external program is expected to receive an eBay developer keyset and an Anthropic API key through
config.env. It also processes user photographs and can interact with eBay to upload content and create live listings. Consequently, the unaudited dependency operates across security-sensitive trust boundaries.An attacker who compromises the external distribution account, download artifact, hosting chain, or a user's local
listblitz/directory could substitute a maliciousorchestrate.py. Because the agent is instructed to invoke that filename, the substituted program could execute with the agent process's local permissions and access available credentials and files.The audited file does include a useful publication guardrail:
markdown - NEVER run `--live` witho ...[truncated 2105 chars]- Remediation
View remediation
Remediation Suggestions
- Bundle the reviewable source code for
orchestrate.pyand all required local modules with the skill, or reference a public, auditable source repository. - Pin the dependency to an immutable release identifier or commit rather than a mutable download page.
- Publish a SHA-256 or stronger digest and a developer signature for every supported artifact. Verify both before execution and fail closed on mismatch.
- Maintain a dependency lockfile and use reproducible builds where practical.
- Document the minimum required eBay and Anthropic permissions. Use separate, least-privilege, revocable credentials rather than broadly scoped production keys.
- Store credentials in an approved secret manager or protected environment injection mechanism rather than relying on an unspecified plaintext configuration workflow.
- Run the external pipeline in a sandbox or container with restricted filesystem access, no unnecessary network destinations, a read-only code mount, and limited process privileges.
- Enforce the draft-versus-live approval state outside the external executable. Bind approval to a digest of the exact listing payload and verify that digest immediately before publication.
- Restrict outbound network access to documented eBay and Anthropic endpoints where operationally feasible.
- Audit the complete ListBlitz package before deployment and repeat the audit whenever its pinned version or verified artifact changes.
- Bundle the reviewable source code for
