T09 · Insecure Skill Coding Practices
- Location
scripts/read_article.py:69- Finding
Chromium Sandbox Disabled for Untrusted Web Content
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill appears intended to read X articles aloud, but it stores an X login session locally and uses it in a browser with weak scoping and browser sandboxing disabled.
Review before installing. Use only with X article URLs you trust, understand that it stores reusable X session data under the skill directory, and avoid sharing or backing up that directory. Prefer a version that validates x.com article URLs, removes --no-sandbox, avoids writing plaintext state.json, pins dependencies, and documents cleanup of saved login state.
scripts/read_article.py:69Chromium Sandbox Disabled for Untrusted Web Content
scripts/read_article.py:47Missing URL Allowlist Permits Navigation Outside the Declared X Article Scope
scripts/auth_setup.py:73Authenticated Browser State Written to an Unprotected Plaintext File
SKILL.md:27Unpinned Third-Party Package and Browser Installation
The declared purpose focuses on reading an article aloud, but the documented behavior also includes authentication setup, persistent session storage, and browser-driven login management. That mismatch is dangerous because users or agent frameworks may authorize the skill for simple TTS while unknowingly granting access to account sessions and login flows, increasing credential and privacy risk.
The skill documentation describes capabilities that imply shell execution, file reads/writes, browser automation, and persistent local storage, but it declares no explicit tool scope or permission boundary. That increases the chance an agent may invoke powerful operations without clear user-visible restriction or review, especially because the skill launches scripts and stores browser state.
The trigger phrases include broad commands like '读出来', '朗读', and 'read aloud', which are common everyday requests and may cause unintended activation. In context, unintended activation is more concerning because this skill can open URLs, run scripts, and potentially reuse authenticated browser state, so a casual utterance could trigger more powerful behavior than expected.
The file’s user-facing docstring and runtime messages are written entirely in Chinese, which imposes a specific language on users without opt-in or alternative language support. This is a natural-language policy concern because the skill does not offer any language/locale choice or explain that it is intentionally region-specific.
The script launches a persistent browser context, has the user log into X, and then saves both the browser profile and storage state locally. That creates reusable authenticated session material for an account, which is more sensitive than what is necessary for a simple text-to-speech reader unless the need for authenticated access is explicitly justified and tightly scoped. In this skill context, reading articles aloud does not obviously require long-lived account session persistence, so the capability increases the risk of credential/session misuse if the local files are accessed by other code or users on the system.
subprocess module calls execute external commands. Without careful input validation, this enables command injection.
cmd.append(content)
try:
subprocess.run(cmd, check=True)
print(f"\n✅ {'音频已保存:' + output_file if output_file else '朗读完毕'}")
except KeyboardInterrupt:
print("\n⏹️ 已停止")
The file states that the skill automatically detects Chinese vs English and picks the appropriate voice, and later maps Chinese to Tingting and English to Samantha. This imposes a locale/language behavior by default rather than offering a user language or voice preference as an opt-in.
The documentation states the authentication data is fully isolated from other skills, but the implementation only writes files under a local directory and does not enforce any OS-level isolation, access controls, or sandboxing. This can mislead users into overtrusting the storage model and underestimating the exposure of saved session data if other local processes or skills can read the same filesystem location.
The code automatically classifies text as Chinese or English and then selects a corresponding voice, while the file-level documentation and output messages are also fixed in Chinese. This imposes a language/locale choice by default rather than explicitly asking the user for their preferred language or narration locale.
No suspicious patterns detected.