T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:11- Finding
Mandatory Access to External Credential-Bearing Configuration
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is for SEO and competitor research, but it asks the agent to read broad local secrets and run unaudited external code before doing the work.
Review before installing. Only use this skill in a controlled environment where /tmp/powerful-trendplus is trusted, immutable, and owned by you; replace broad token loading with least-privilege credentials; and require explicit confirmation before any run that reads secrets, writes to Sheets, accesses internal databases, or calls third-party APIs.
SKILL.md:11Mandatory Access to External Credential-Bearing Configuration
SKILL.md:15Sourcing an External Environment File Before Executing an Unaudited Script
The command explicitly sources .env.local, causing the runtime to ingest all secrets from a local environment file before running the research script. This is a classic credential-access pattern that can expose or misuse secrets if the skill is triggered unexpectedly, if the script behavior changes, or if downstream tools log or transmit loaded values.
cd /tmp/powerful-trendplus
source .env.local 2>/dev/null
python3 scripts/run_full_research.py
The trigger phrases are broad and generic, so the skill could activate on ordinary conversation about products, SEO, or competitors without clear intent to run it. In an agent system that can load secrets and external integrations, overbroad activation materially raises the risk of unintended execution and data access.
The skill metadata and instructions are written entirely in Chinese while also including English trigger phrases, but there is no statement that the user can choose the interaction language. This can amount to a language policy issue because the skill appears to impose a specific language without opt-in or documented justification.
The skill explicitly discloses where tokens are stored and instructs automatic loading from local files and shell configuration, which normalizes credential access as part of routine execution. In an adversarial or mis-triggered context, that makes secret discovery and use significantly easier and increases the blast radius beyond the stated task.
The skill instructs access to multiple credentials and integrations that exceed the narrowly described research function, including OAuth- and database-backed systems. Even if intended for convenience, expanding the data/control surface in a documentation-driven agent increases the chance of unnecessary secret exposure and unauthorized access during execution.
Declaring Google Sheets output and MySQL internal data comparison broadens the skill from analysis into data egress and internal data access. That creates unnecessary pathways for sensitive business data to be read or exported without clear scope boundaries in the manifest.
No suspicious patterns detected.