T09 · Insecure Skill Coding Practices
- Location
SKILL.md:47- Finding
BigCommerce API Token Exposed Through Command-Line Arguments
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a real BigCommerce catalog updater, but it can autonomously rewrite live product content across a store with weak confirmation, validation, and credential-handling safeguards.
Install only if you are prepared for it to modify live BigCommerce product content in bulk. Use a test store first, export or back up existing catalog content, use a narrowly scoped token, avoid putting tokens on the command line, review every generated update file before pushing it, and consider replacing the setup with a pinned virtual environment. This is not evidence of malicious intent, but the current safeguards are weak for production catalog writes.
SKILL.md:47BigCommerce API Token Exposed Through Command-Line Arguments
SKILL.md:33Unpinned Dependency Installation Bypasses System Package Protections
scripts/bc_optimizer.py:241Unvalidated Agent-Generated HTML and Product Updates Are Written to the Storefront
The skill is designed to autonomously update live BigCommerce product titles and descriptions page by page without pausing, but it does not present a prominent warning or confirmation requirement before performing those bulk writes. In a production ecommerce environment, accidental execution can cause widespread content corruption, SEO damage, brand inconsistency, and time-consuming rollback efforts.
The skill performs file reads/writes and networked API calls but does not declare any explicit tool scope or permissions boundaries. That increases the chance of over-privileged execution, weak reviewability, and unintended access to local files or external services beyond what the user expects.
The skill persists execution state in progress.json and is explicitly designed to resume in-progress bulk modifications automatically. Persistent state itself is not inherently malicious, but in this context it can cause unintended continuation of prior write operations, especially if the environment is reused, the file is stale, or a later invocation occurs with ambiguous intent.
description: >
Autonomous BigCommerce product content optimizer. Bulk-update, rewrite, optimize,
or generate product titles and descriptions on a BigCommerce store. Triggers on
"optimize my BigCommerce products", "rewrite product descriptions", "update product
content", "improve my store listings", "bulk update BigCommerce", or when BigCommerce
API credentials (store hash, API token) are provided for content work. Handles the
full lifecycle: fetching products page-by-page, generating improved content, updating
The trigger phrases are broad enough that ordinary requests like improving listings or providing BigCommerce credentials could activate an autonomous bulk-update workflow. In this skill's context, that is dangerous because activation can quickly lead to live product rewrites across many items without a narrow, explicit user command.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# ---------------------------------------------------------------------------
# Constants
# ---------------------------------------------------------------------------
BASE_URL = "https://api.bigcommerce.com/stores/{store_hash}/v3"
PROGRESS_FILE = "progress.json"
RATE_LIMIT_PAUSE = 3 # seconds to wait when rate-limited
MAX_RETRIES = 5 # max retries per request on rate limit / transient error
No suspicious patterns detected.