Incomplete referenced artifact analysis
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md node scripts/dy-publish.js --ep 02 --time "2026-10-15 07:00"
Security audit
Security checks for vulnerabilities and agentic risk
This skill fits Douyin publishing, but its cleanup can delete unintended videos and its instructions require disabling sandbox protection.
Review before installing. Preserve sandbox protection and use a dedicated browser profile. Avoid DEL=1 until deletion checks exact video identity and scheduled status. Configure private output paths and make screenshots optional. Publishing dry runs still upload the video and save a screenshot. Verify actual account results before repeating failed batch items.
Referenced artifact was not completely inspected
node scripts/dy-publish.js --ep 02 --time "2026-10-15 07:00"
Referenced artifact was not completely inspected
node scripts/dy-publish.js --file a.mp4 --title "标题" --desc "正文" \
Referenced artifact was not completely inspected
node scripts/dy-publish.js --ep 02 --time "2026-10-15 07:00" --dry
Referenced artifact was not completely inspected
脚本逐条调用 `dy-publish.js`,日志写 `dy-batch.log`,末尾输出成功/失败计数。
Referenced artifact was not completely inspected
- `scripts/dy-publish.js` — 主发布脚本
Referenced artifact was not completely inspected
zsh scripts/batch-dy.sh
Referenced artifact was not completely inspected
START_EP=30 END_EP=30 START_DAY=29 START_HOUR=07 zsh scripts/batch-dy.sh
Referenced artifact was not completely inspected
- `scripts/batch-dy.sh` — 批量双更排期
Referenced artifact was not completely inspected
node scripts/dy-status-list.js 全部 # 概览
Referenced artifact was not completely inspected
- `scripts/dy-status-list.js` — 按审核状态快速筛
Referenced artifact was not completely inspected
node scripts/dy-queue.js 全部 # 卡片式滚动累积抓取(虚拟列表,必须用这个)
Referenced artifact was not completely inspected
8. **列表是虚拟滚动**:`body.innerText` 一次只渲染约 12 条,必须滚动累积去重(`dy-queue.js`)。
Referenced artifact was not completely inspected
- `scripts/dy-queue.js` — 虚拟列表滚动累积抓取(对账主力)
Referenced artifact was not completely inspected
NAME="怎么活得更好" DESC="系列简介" COVER=/path/cover.png node scripts/dy-create-collection.js
Referenced artifact was not completely inspected
- `scripts/dy-create-collection.js` — 建合集
The troubleshooting table recommends setting dangerouslyDisableSandbox: true as a routine fix for unresponsive clicks, without establishing that sandboxing caused the problem or explaining the security consequences. If honored by the execution environment, this removes an isolation boundary and can allow compromised scripts or injected commands to access host resources beyond the sandbox. Browser automation involving an authenticated publishing account increases the potential consequences, although this file does not itself demonstrate exploitation or malicious intent.
The script selects the IDX-th visible deletion control after a keyword search without verifying the work's identity, scheduled status, or duplication. With DEL=1, it can therefore delete a legitimate, potentially already-published work using the authenticated account; the duplicate-cleanup context makes this particularly dangerous because users may reasonably expect only redundant scheduled posts to be affected. The default dry-run gate reduces accidental execution but does not validate the target when deletion is enabled.
Without declared permissions the skill's intent is opaque and cannot be validated.
The skill explicitly requires dangerouslyDisableSandbox: true without explaining the loss of isolation or limiting the exception. Running its scripts outside the sandbox increases the potential consequences of compromised dependencies or script behavior, particularly because the workflow controls a browser logged into an account with publishing and deletion capabilities; the referenced scripts were not supplied, so their safeguards cannot be verified.
The script saves screenshots to fixed local PNG paths without a comment, prompt, or log disclosing that account-page content will be persisted. The first screenshot is written before the dry-run check, so even a non-deleting run creates or overwrites a file that may contain private account information.
The screenshot can persist account content visible on the page to a fixed local PNG file, potentially overwriting an existing capture. No prompt, log, or explanatory comment discloses this action; the stated duplicate-title search purpose does not clearly imply saving screenshots.
The screenshot creates or overwrites a local PNG that may contain private creator-dashboard information. Unlike the stated status-filtering and list-extraction actions, this persistent capture has no accompanying comment, confirmation, or user-facing log disclosing the file write.
The script automatically saves screenshots of an authenticated creator page to predictable local paths, potentially retaining unpublished collection details or visible account information without explicit consent. The first screenshot is saved even in DRY mode; although these appear to be debugging artifacts rather than malicious collection, backups, synchronization, or principals with access to the files could expose their contents. No external transmission or broad file permissions are demonstrated, so the risk is limited and conditional.
Lines 229 and 267 write screenshots of the creator page to fixed local paths without a confirmation, log message, or explanatory comment disclosing these writes. This persists page content beyond the publishing workflow, and the first screenshot is saved even during a dry run.