T09 · Insecure Skill Coding Practices
- Location
SKILL.md:56- Finding
Chromium Process Sandbox Disabled During Sensitive Mailbox Automation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is for ProtonMail browser automation, but it includes bot-detection bypass and disables Chromium sandboxing while handling sensitive email access.
Review before installing. This skill can access and send mail from a ProtonMail account, asks users to provide credentials through environment variables, and includes automation-evasion settings plus disabled browser sandboxing. Use only on accounts you control, avoid privileged execution, pin dependencies, and remove stealth and no-sandbox launch arguments before use.
SKILL.md:56Chromium Process Sandbox Disabled During Sensitive Mailbox Automation
SKILL.md:6Unpinned Playwright Dependency and Browser Installation
The skill directly instructs impersonation of human browsing behavior by hiding automation fingerprints. This materially increases abuse potential because it is designed to evade detection by the service operator while automating access to a sensitive email platform.
The skill advertises login, inbox reading, sending, and mailbox management for an encrypted email service but does not prominently warn about privacy, account takeover, sending abuse, or compliance risks. In context, the skill handles highly sensitive communications, so underemphasizing risk makes misuse and unsafe deployment more likely.
This is a duplicate instance of the same unpinned npx playwright reference in the metadata. Unpinned package execution creates a supply-chain risk, especially in a skill that logs into ProtonMail and can access or send private email.
The requirements section instructs npx playwright install chromium without binding the toolchain to an exact Playwright version. While the browser install itself is common, leaving the package version floating undermines reproducibility and increases supply-chain exposure.
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
# Ubuntu/Debian
sudo apt-get update
sudo apt-get install -y libnss3 libnspr4 libatk1.0-0 libatk-bridge2.0-0 libcups2 libdrm2 libxkbcommon0 libxcomposite1 libxdamage1 libxfixes3 libxrandr2 libgbm1 libasound2 libpango-1.0-0 libcairo2
# Raspberry Pi / ARM
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
# Ubuntu/Debian
sudo apt-get update
sudo apt-get install -y libnss3 libnspr4 libatk1.0-0 libatk-bridge2.0-0 libcups2 libdrm2 libxkbcommon0 libxcomposite1 libxdamage1 libxfixes3 libxrandr2 libgbm1 libasound2 libpango-1.0-0 libcairo2
# Raspberry Pi / ARM
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
# Ubuntu/Debian
sudo apt-get update
sudo apt-get install -y libnss3 libnspr4 libatk1.0-0 libatk-bridge2.0-0 libcups2 libdrm2 libxkbcommon0 libxcomposite1 libxdamage1 libxfixes3 libxrandr2 libgbm1 libasound2 libpango-1.0-0 libcairo2
# Raspberry Pi / ARM
The documentation explicitly includes bot-detection evasion measures such as disabling automation indicators and redefining navigator.webdriver to impersonate human browsing. This is not necessary for ordinary mailbox automation and crosses into stealth behavior that can facilitate policy evasion, abuse of third-party services, and concealment of automated access.
The troubleshooting guidance again uses npx playwright install chromium without a pinned version. Repeatedly encouraging floating package resolution increases the chance users execute unexpected code from the package registry.
The manifest only states browser-based email management functionality. The documentation adds a separate capability of sourcing credentials from process environment variables, which is credential-access behavior not declared in the skill description and may exceed the expected scope for a narrowly described mail-management skill.
No suspicious patterns detected.