T09 · Insecure Skill Coding Practices
- Location
src/modules/x_fetcher.py:124- Finding
Chromium Sandbox Disabled While Rendering Untrusted Third-Party Pages
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This AI news skill mostly does what it says, but its browser scraper disables Chromium sandboxing while visiting third-party pages, which creates a review-worthy safety risk.
Install only if you are comfortable with a network-heavy scraper that contacts many third-party sites and generates local reports from untrusted content. Run it as an unprivileged user or in a container, avoid opening generated Markdown in permissive renderers, and prefer a version that removes Chromium no-sandbox flags and pins dependencies.
src/modules/x_fetcher.py:124Chromium Sandbox Disabled While Rendering Untrusted Third-Party Pages
src/modules/report_generator.py:265Untrusted Feed Content Is Written to Markdown Without Context-Aware Escaping
This finding indicates the skill has undeclared X/Twitter/Nitter scraping, browser automation via Playwright, and targeted social-media collection that are not transparently disclosed in the primary description. Undocumented browser automation and targeted scraping materially increase risk because they expand network reach, can interact with dynamic sites, and may collect or transmit more data than a user expects.
This finding indicates the skill has undeclared X/Twitter/Nitter scraping, browser automation via Playwright, and targeted social-media collection that are not transparently disclosed in the primary description. Undocumented browser automation and targeted scraping materially increase risk because they expand network reach, can interact with dynamic sites, and may collect or transmit more data than a user expects.
The README content is presented in Chinese throughout, with no indication that the user can choose another language or that the locale restriction is intentional and documented as a regional requirement. Under the policy, forcing a specific language without user opt-in is a natural-language policy concern.
The skill advertises capabilities that require file read/write and outbound network access, but it does not declare any tool scope or permissions boundaries. This can cause the runtime to grant broader access than users expect, reducing transparency and increasing the risk of unintended data access or exfiltration through third-party requests.
The skill describes automatic aggregation from many third-party sources but does not warn users that running it will generate outbound requests to numerous external domains. Lack of disclosure is dangerous because it can expose user IP/network metadata, trigger organization policy issues, and surprise users in restricted or privacy-sensitive environments.
The natural-language description 'AI Daily News Aggregator 主入口' mixes English with Chinese and indicates the skill is presented in Chinese by default. The file contains no natural-language indication that users can opt into another language or locale, which conflicts with the policy against forcing a specific language without user choice.
The module docstring is written entirely in Chinese and provides no indication that users can choose another language or locale. The policy explicitly flags language or locale constraints when they are imposed without user opt-in or documented justification.
This code uses Chinese-only natural-language strings in the module description and throughout generated report content, such as headings and labels, which effectively forces a specific language/locale. Under the policy, locale-specific behavior should either offer user opt-in or be clearly documented as intentionally region-specific.
This file uses Chinese natural-language strings in the module description, docstrings, and log messages, which can impose a specific language without evidence of user opt-in. The policy explicitly flags language or locale constraints when the skill forces a specific language and does not offer a choice.
This code explicitly sets locale='en-US', timezone_id='America/New_York', and Accept-Language: en-US,en;q=0.9 for all browsing sessions. Under the policy, forcing a specific language/locale without user opt-in is a natural-language policy violation unless the constraint is justified or configurable.
This markdown file explains that the skill collects content from RSS, social media, APIs, and web scraping sources, and later states that reports are generated in the local reports/ directory. Because the README is the user-facing description for a skill that performs network access and writes output files, it should explicitly disclose these behaviors and any privacy or system-impact considerations.
The dependency is specified with a lower bound only, so builds may resolve to different versions over time and can unexpectedly pull in vulnerable or breaking releases. In a skill that aggregates external content and uses parsing/network libraries, this weakens supply-chain control and makes security posture hard to verify.
pyyaml>=6.0.3
feedparser>=6.0.12
requests>=2.33.1
beautifulsoup4>=4.12.0
PyYAML has multiple historical advisories, and because the version is not pinned, there is no way to verify that installations avoid affected releases. If this skill parses YAML from untrusted or indirectly influenced sources, vulnerable versions could enable serious parser misuse such as unsafe deserialization or improper input handling.
The feedparser dependency is unpinned, which allows environment-dependent installs and makes it impossible to guarantee the same audited package version everywhere. Because this skill consumes external feeds, parser behavior and security fixes should be tightly controlled.
pyyaml>=6.0.3
feedparser>=6.0.12
requests>=2.33.1
beautifulsoup4>=4.12.0
lxml>=4.9.0
feedparser has known advisories and the lack of a pinned version means the deployed package could still be an affected release. Since this skill ingests untrusted RSS/Atom content from external sources, parser vulnerabilities are more relevant in context.
An unpinned requests version means future installs may select different releases, including ones with unresolved security issues or changed TLS/redirect behavior. For a network-heavy news collection skill, that increases supply-chain and operational risk.
pyyaml>=6.0.3
feedparser>=6.0.12
requests>=2.33.1
beautifulsoup4>=4.12.0
lxml>=4.9.0
playwright>=1.40.0
requests has several known advisories, and without exact version pinning it is impossible to confirm whether installs are patched. In a skill that performs outbound HTTP requests to many sources, issues involving redirects, credential handling, or TLS behavior can materially affect security.
beautifulsoup4 is unpinned, so deployments are not reproducible and may receive unreviewed upstream changes. While not directly proving exploitation, this creates avoidable supply-chain uncertainty in a scraper/parser workflow.
pyyaml>=6.0.3
feedparser>=6.0.12
requests>=2.33.1
beautifulsoup4>=4.12.0
lxml>=4.9.0
playwright>=1.40.0
aiohttp>=3.9.0
lxml is a security-sensitive parser library and leaving it unpinned can expose deployments to parser-related vulnerabilities or inconsistent behavior across environments. In a skill that processes untrusted remote content, this is more concerning than a purely local utility dependency.
feedparser>=6.0.12
requests>=2.33.1
beautifulsoup4>=4.12.0
lxml>=4.9.0
playwright>=1.40.0
aiohttp>=3.9.0
fake-useragent>=1.4.0
lxml has a substantial advisory history, and leaving the version unpinned makes it impossible to verify whether the parser in use is safe. Because the skill parses untrusted web content, parser-related flaws can have a more meaningful impact here than in a closed-input application.
playwright is unpinned, which allows browser automation components to drift across installations and may introduce unexpected security or sandbox changes. Because this skill may render untrusted web pages, deterministic versioning is important.
requests>=2.33.1
beautifulsoup4>=4.12.0
lxml>=4.9.0
playwright>=1.40.0
aiohttp>=3.9.0
fake-useragent>=1.4.0
aiohttp is unpinned, so network-facing behavior and security fixes cannot be verified for any given installation. For software that fetches remote data continuously, this undermines reproducibility and vulnerability management.
beautifulsoup4>=4.12.0
lxml>=4.9.0
playwright>=1.40.0
aiohttp>=3.9.0
fake-useragent>=1.4.0
aiohttp has known advisories, and the absence of an exact version prevents verification that the deployed release contains necessary fixes. While the actual exploitability depends on how the library is used, the unpinned network dependency creates avoidable uncertainty for an internet-facing skill.
fake-useragent is unpinned, allowing builds to consume varying upstream versions without review. Even if lower risk than core parser/network libraries, it still contributes to unnecessary supply-chain unpredictability.
lxml>=4.9.0
playwright>=1.40.0
aiohttp>=3.9.0
fake-useragent>=1.4.0
This manifest contains substantial natural-language content in Chinese alongside English identifiers and labels, but does not state whether the skill is intended specifically for Chinese-speaking users or whether other locales are supported. Under the language/locale policy rule, forcing or implicitly assuming a locale without user choice or justification can be a policy concern.