Incomplete referenced artifact analysis
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md - 核查原创:`node scripts/check-original.js`
Security audit
Security checks for vulnerabilities and agentic risk
This video-publishing skill needs review because it requires disabling execution isolation and can change post descriptions or publish without fully verifying the requested date.
Before unattended use, correct full-date verification and preserve existing descriptions during rescheduling. Retain execution isolation with narrowly scoped browser access and use a dedicated browser profile. The --dry-run option uploads your video and saves a real platform draft; review its content, schedule, and originality declaration.
Referenced artifact was not completely inspected
- 核查原创:`node scripts/check-original.js`
Referenced artifact was not completely inspected
node scripts/check-original.js [--all]
Referenced artifact was not completely inspected
- `scripts/check-original.js` — 原创声明状态核查
Referenced artifact was not completely inspected
- **对账**:`node scripts/list-all.js` — 一次拉全量列表(标题/时间/原创状态),
Referenced artifact was not completely inspected
node scripts/list-all.js
Referenced artifact was not completely inspected
- `scripts/list-all.js` — 全量列表导出,用于对账「哪些发了哪些没发」
Referenced artifact was not completely inspected
- 新增 `list-all.js`:一次性拉全量列表,用于对账
Without declared permissions the skill's intent is opaque and cannot be validated.
The prerequisites explicitly require dangerouslyDisableSandbox: true without explaining the loss of isolation or limiting its use. Running Node scripts and dependencies outside the sandbox can expose host files and network resources if that code is compromised; the authenticated Chrome debugging session also provides a path to account actions. A separate Chrome profile reduces browser-profile mixing but does not restore execution isolation.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Chrome 是按请求的 Host 头生成 webSocketDebuggerUrl 的。
发 Host: 127.0.0.1 会拿到 ws://127.0.0.1/devtools/...(没有端口)→ ws 去连 80 → ECONNREFUSED。
curl 能连上是因为它发的是 Host: 127.0.0.1:9222。
http.get({ host: '127.0.0.1', port: 9222, path, headers: { Host: '127.0.0.1:9222' } })
The document explicitly requires running Bash with dangerouslyDisableSandbox: true, removing execution isolation to work around a local networking issue. Publishing scripts would then run with the host user's permissions, increasing the consequences of compromised scripts or dependencies, including access to local files and the authenticated browser session. A dedicated Chrome profile reduces profile mixing but does not replace execution isolation.
The --dry-run check occurs only after uploading the video and clicking '保存草稿', so a documented form-filling rehearsal can transfer private content and persist a draft in the authenticated remote account. Although this mode does not click Publish and the destination is the intended publishing platform, those persistent side effects exceed typical dry-run expectations and may expose unreleased content to the platform or other authorized account users.