T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:137- Finding
Excessive Production Credential Requirements Violate Least-Privilege Principles
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a plausible revenue-analysis guide, but it asks for broad live business credentials and gives inconsistent privacy assurances around customer data.
Review before installing. Use restricted read-only API keys, sandbox data where possible, avoid putting long-lived production secrets directly into a shared agent environment, and do not enable Slack or Google Sheets exports unless customer identifiers are redacted or explicitly approved under your privacy obligations.
SKILL.md:137Excessive Production Credential Requirements Violate Least-Privilege Principles
Referenced artifact was not completely inspected
"files": ["SKILL.md"],
The skill instructs users to place Google credentials in an environment variable named as an API key, pointing to a local credentials JSON file. This mixes secret-management models and can cause operators to expose service account credentials through environment dumps, logs, process listings, or accidental reuse in downstream tooling, increasing the risk of credential compromise and unauthorized access to Google Sheets or broader Google resources.
export MAILCHIMP_LIST_ID="your_list_id"
# Google Sheets (output reports)
export GOOGLE_SHEETS_API_KEY="your_google_credentials.json"
export GOOGLE_SHEET_ID="your_sheet_id"
# Optional: CRM/Analytics
The skill claims it will not analyze or export customer PII, yet its example output includes a specific customer email address and individualized churn analysis. This contradiction normalizes handling and surfacing personal data in outputs, which can mislead operators about privacy guarantees and lead to unauthorized disclosure of customer information in chats, logs, Slack alerts, or reports.
The safety section asserts the skill will not analyze or export customer PII, but the preceding churn alert example demonstrates exactly that behavior by exposing an email address and personalized account data. False safety assurances are dangerous because they encourage trust and broader deployment while concealing real privacy and compliance risks.
The description says to use the skill when the user needs "LTV optimization, churn prevention, or strategic revenue growth," which are broad, common business goals rather than specific activation phrases or constraints. This can make it unclear when the skill should activate versus when a general business-analysis request should be handled by something else.
The skill promotes integrations with payment, email, analytics, CRM, messaging, and spreadsheet systems that process sensitive customer and revenue data, but it does so without an upfront privacy and data-handling warning. In context, this increases the chance that users connect high-sensitivity systems without understanding what data may be accessed, correlated, or transmitted to third-party destinations like Slack and Google Sheets.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Verify Stripe connection
curl https://api.stripe.com/v1/account \
-H "Authorization: Bearer $STRIPE_API_KEY"
# Test Mailchimp connection
No suspicious patterns detected.