T09 · Insecure Skill Coding Practices
- Location
SKILL.md:32- Finding
Chromium Sandbox Disabled During Processing of Remote Content
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is for a sensitive church account workflow, but it gives broad automation instructions that include stealth browsing and unsafe session handling.
Review carefully before installing. Only use this with accounts and church data you are authorized to access, avoid stealth or detection-bypass techniques, remove the no-sandbox browser flag, and do not store reusable session tokens in shared temporary paths. Sensitive reads or changes should be narrowly scoped and confirmed by the user each time.
SKILL.md:32Chromium Sandbox Disabled During Processing of Remote Content
SKILL.md:27Reusable Authentication State Stored in a Predictable Temporary File
SKILL.md:32Deliberate Evasion of Service Anti-Automation Detection
The skill handles credentials, session persistence, and access to highly sensitive church account areas, including membership, finance, and temple-related data, but it provides no upfront warning, consent flow, or privacy guardrails. It even recommends storing reusable auth state under /tmp, which can expose tokens if the host is shared or compromised, making the overall context especially sensitive and high impact.
The manifest description says to use the skill for logging in, roster lookups, managing callings, viewing temple recommend status, directory access, and 'any other LCR/church website automation,' which is excessively broad. That breadth can cause the skill to activate for many sensitive tasks without clear limits, increasing the chance of over-collection, unintended account actions, or use in contexts the user did not explicitly authorize.
The top-level description 'Automate login and tasks on churchofjesuschrist.org' is too general for a high-sensitivity domain. In context, the site includes protected account, directory, finance, and temple workflows, so vague activation language makes accidental or overly broad use more dangerous than it would be for a low-risk website.
The skill explicitly recommends playwright-stealth and states it 'avoids detection,' which introduces anti-detection tradecraft unrelated to ordinary account automation. In a skill that automates access to sensitive church systems and member data, normalizing stealth features increases the chance of policy evasion, abuse, and covert access.
The sample code disables browser automation signals using --disable-blink-features=AutomationControlled and applies stealth behavior, which is a direct mechanism for concealing automation from the target service. Because this skill targets authenticated church resources containing sensitive membership, finance, and temple-related information, such concealment materially raises misuse risk.
No suspicious patterns detected.