Security audit
Security checks for vulnerabilities and agentic risk
The skill is not clearly malicious, but it asks for Etsy credentials and can create shop drafts while its description overstates and misstates what the code actually does.
Review before installing. Only use this with an Etsy account where you are comfortable granting API write access, and inspect or edit the hardcoded LISTINGS data first because the script will create those specific draft listings rather than deriving listings from your own product files. The missing OAuth helper also means setup is incomplete as packaged.
Credentials or environment variables flow to a network sink. This is a high-confidence indicator of credential exfiltration.
"state": "draft",
}
resp = requests.post(
f"{BASE_URL}/applications/shops/{ETSY_SHOP_ID}/listings",
headers=get_headers(),
json=payload,
The manifest overstates the skill's capabilities, claiming it creates listings from files, handles tagging, manages listings, and publishes drafts, while the documented behavior is much narrower. Security reviewers and users may trust the skill with sensitive credentials or business workflows under false assumptions, which increases the chance of misuse and unsafe operation.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
3. Save as secrets: `ETSY_CLIENT_KEY` and `ETSY_CLIENT_SECRET` in [Settings > Advanced](/?t=settings&s=advanced)
4. Get your Shop ID from your Etsy shop URL (etsy.com/shop/{shop_id})
5. Save as secret: `ETSY_SHOP_ID`
6. Run the OAuth helper to get your access token
## OAuth Setup (Required)
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
3. Save as secrets: `ETSY_CLIENT_KEY` and `ETSY_CLIENT_SECRET` in [Settings > Advanced](/?t=settings&s=advanced)
4. Get your Shop ID from your Etsy shop URL (etsy.com/shop/{shop_id})
5. Save as secret: `ETSY_SHOP_ID`
6. Run the OAuth helper to get your access token
## OAuth Setup (Required)
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
3. Save as secrets: `ETSY_CLIENT_KEY` and `ETSY_CLIENT_SECRET` in [Settings > Advanced](/?t=settings&s=advanced)
4. Get your Shop ID from your Etsy shop URL (etsy.com/shop/{shop_id})
5. Save as secret: `ETSY_SHOP_ID`
6. Run the OAuth helper to get your access token
## OAuth Setup (Required)
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
3. Save as secrets: `ETSY_CLIENT_KEY` and `ETSY_CLIENT_SECRET` in [Settings > Advanced](/?t=settings&s=advanced)
4. Get your Shop ID from your Etsy shop URL (etsy.com/shop/{shop_id})
5. Save as secret: `ETSY_SHOP_ID`
6. Run the OAuth helper to get your access token
## OAuth Setup (Required)
The skill requests users to store secrets and use networked scripts, but the manifest does not declare any tool scope or permissions. This weakens transparency and reviewability, making it easier for a skill to access environment variables and external services without clear user expectation or policy enforcement.
The manifest says the skill 'Handles listing creation, tagging, pricing, and draft publishing,' which implies it performs publication-related actions. However, the in-file documentation states 'Manually publish drafts in your Etsy shop dashboard' and that the bot only creates drafts, indicating the skill does not itself publish listings. This is a direct description-behavior mismatch within the documented intent.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
ETSY_CLIENT_KEY = os.environ.get("ETSY_CLIENT_KEY", "")
ETSY_CLIENT_SECRET = os.environ.get("ETSY_CLIENT_SECRET", "")
ETSY_SHOP_ID = os.environ.get("ETSY_SHOP_ID", "") # Your shop ID
BASE_URL = "https://api.etsy.com/v3"
# OAuth token (set manually after running oauth helper)
ETSY_ACCESS_TOKEN = os.environ.get("ETSY_ACCESS_TOKEN", "")
The manifest says the skill creates listings from existing digital product files such as PDFs, templates, and spreadsheets, and manages listing metadata around those inputs. In this file, listings are predefined in code with static titles/descriptions and there is no code that reads, inspects, or derives listing data from existing product files, so the actual behavior is manual posting of hardcoded listings rather than file-based auto-creation.
The file introduces the skill as 'Auto-create digital product listings on Etsy,' while the later 'After Creation' section states the bot creates only drafts and publishing must be done manually. This is not merely incomplete wording; it presents a broader automated listing-management intent up front that is contradicted by the later operational guidance.
The manifest states the skill handles listing creation, tagging, pricing, and draft publishing. Here, the payload explicitly sets state to "draft" and the rest of the file only creates listings; there is no code to publish drafts, update listings, or perform broader listing management.
This code performs an outbound HTTP POST to Etsy that transmits listing content and shop identifiers. While the script logs success and failure afterward, it does not disclose before the operation that data will be sent to Etsy, and the module docstring does not explicitly warn about that network transmission.
No suspicious patterns detected.