T09 · Insecure Skill Coding Practices
- Location
scripts/capture-rankings.mjs:332- Finding
Arbitrary URL Navigation in an Unsandboxed Chromium Process
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill mostly matches its advertised OpenRouter-to-Feishu report purpose, but its browser capture script is under-restricted and can be pointed at arbitrary sites while running Chromium without sandboxing.
Review before installing. This skill is suitable only in an environment where you are comfortable with automated Feishu document creation and daily reporting. The publisher should remove or allowlist the URL argument, avoid running Chromium without sandboxing where possible, restrict network egress, validate manifest file paths before upload, and update the flagged dependencies.
scripts/capture-rankings.mjs:332Arbitrary URL Navigation in an Unsandboxed Chromium Process
scripts/validate-screenshots.mjs:10Manifest-Controlled File Paths Can Reach the Feishu Upload Workflow
extract-zip 2.0.1 is a real supply-chain risk because archive extraction bugs involving symlink handling can let a crafted archive write files outside the intended destination. In this dependency tree it is brought in by Puppeteer browser-management tooling, so exploitation would require the skill to process or download attacker-influenced archives, but if that occurs it can lead to arbitrary file overwrite and possible code execution or persistence.
ip-address 10.2.0 has reported address-classification flaws that can mis-handle IPv4-mapped, NAT64, or CIDR-suffixed inputs, which matters when software relies on it to decide whether a destination is private, loopback, or otherwise restricted. In this lockfile it is only a transitive dependency of proxy-related packages, and there is no direct evidence in this file that the skill performs security-sensitive SSRF filtering with it, so the issue is real but contextually less exposed here.
ws 8.20.1 is affected by a memory-exhaustion denial-of-service issue where an attacker can send fragmented frames or tiny chunks that cause excessive resource consumption. Because Puppeteer uses WebSocket transport to speak to the browser, this is a real dependency risk, but in this skill the exposure is likely limited to local or trusted DevTools/browser communication unless an attacker can connect to or influence that WebSocket endpoint.
The skill instructs the agent to run local commands and access local files, but it does not declare any explicit tool or permission scope. That mismatch can cause the runtime to grant broader-than-intended capabilities by default, reducing auditability and increasing the chance of unauthorized environment or filesystem access if the skill is reused or modified.
The script uses const url = process.argv[2] || DEFAULT_URL; and then passes that value directly to page.goto(...), so an operator or upstream agent can make it browse to any arbitrary site rather than the intended openrouter.ai/rankings page. In an agent/automation context this expands the skill from a narrowly scoped screenshot tool into a general-purpose headless browser fetcher, which can be abused for SSRF-style access to internal HTTP endpoints, interaction with sensitive intranet pages, or retrieval of untrusted content under the agent's network identity.
The script hardcodes all generated headings and summary text in Chinese, including the markdown report and chat summary. There is no option for language selection or any documented justification that this skill is intended only for a Chinese-language audience, which creates a natural-language locale policy concern.
Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.
"license": "ISC",
"description": "",
"dependencies": {
"puppeteer-core": "^23.11.1"
}
}