T08 · Insecure Dependencies
- Location
scripts/cli/commands/setup.ts:477- Finding
ASR Dependencies and Model Artifacts Are Downloaded Without Cryptographic Integrity Verification
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill matches its Bilibili video-research purpose, with notable caution around optional media/ASR setup and any manually supplied cookies.
Install only if you are comfortable with a Bilibili-focused tool making network requests and writing caches. Run setup plans before applying them, avoid supplying browser cookies unless you understand the account risk, and treat optional ASR setup like installing a large third-party ML stack.
scripts/cli/commands/setup.ts:477ASR Dependencies and Model Artifacts Are Downloaded Without Cryptographic Integrity Verification
scripts/visual/get.ts:484Authentication Cookies Can Be Forwarded to Unvalidated Media URLs
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# 本地环境变量
.env
.env.local
.env.*.local
scripts/prototype/__pycache__/
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# 本地环境变量
.env
.env.local
.env.*.local
scripts/prototype/__pycache__/
__pycache__/
Version and compatibility checking is not dangerous by itself, but when bundled into a skill described as pure Bilibili research it contributes to hidden capability creep. The main risk is transparency and over-privileging rather than direct exploitation of the compatibility logic.
Version and compatibility checking is not dangerous by itself, but when bundled into a skill described as pure Bilibili research it contributes to hidden capability creep. The main risk is transparency and over-privileging rather than direct exploitation of the compatibility logic.
Version and compatibility checking is not dangerous by itself, but when bundled into a skill described as pure Bilibili research it contributes to hidden capability creep. The main risk is transparency and over-privileging rather than direct exploitation of the compatibility logic.
Version and compatibility checking is not dangerous by itself, but when bundled into a skill described as pure Bilibili research it contributes to hidden capability creep. The main risk is transparency and over-privileging rather than direct exploitation of the compatibility logic.
Version and compatibility checking is not dangerous by itself, but when bundled into a skill described as pure Bilibili research it contributes to hidden capability creep. The main risk is transparency and over-privileging rather than direct exploitation of the compatibility logic.
Version and compatibility checking is not dangerous by itself, but when bundled into a skill described as pure Bilibili research it contributes to hidden capability creep. The main risk is transparency and over-privileging rather than direct exploitation of the compatibility logic.
Version and compatibility checking is not dangerous by itself, but when bundled into a skill described as pure Bilibili research it contributes to hidden capability creep. The main risk is transparency and over-privileging rather than direct exploitation of the compatibility logic.
Version and compatibility checking is not dangerous by itself, but when bundled into a skill described as pure Bilibili research it contributes to hidden capability creep. The main risk is transparency and over-privileging rather than direct exploitation of the compatibility logic.
Version and compatibility checking is not dangerous by itself, but when bundled into a skill described as pure Bilibili research it contributes to hidden capability creep. The main risk is transparency and over-privileging rather than direct exploitation of the compatibility logic.
Version and compatibility checking is not dangerous by itself, but when bundled into a skill described as pure Bilibili research it contributes to hidden capability creep. The main risk is transparency and over-privileging rather than direct exploitation of the compatibility logic.
Version and compatibility checking is not dangerous by itself, but when bundled into a skill described as pure Bilibili research it contributes to hidden capability creep. The main risk is transparency and over-privileging rather than direct exploitation of the compatibility logic.
Version and compatibility checking is not dangerous by itself, but when bundled into a skill described as pure Bilibili research it contributes to hidden capability creep. The main risk is transparency and over-privileging rather than direct exploitation of the compatibility logic.
Version and compatibility checking is not dangerous by itself, but when bundled into a skill described as pure Bilibili research it contributes to hidden capability creep. The main risk is transparency and over-privileging rather than direct exploitation of the compatibility logic.
Version and compatibility checking is not dangerous by itself, but when bundled into a skill described as pure Bilibili research it contributes to hidden capability creep. The main risk is transparency and over-privileging rather than direct exploitation of the compatibility logic.
Version and compatibility checking is not dangerous by itself, but when bundled into a skill described as pure Bilibili research it contributes to hidden capability creep. The main risk is transparency and over-privileging rather than direct exploitation of the compatibility logic.
Version and compatibility checking is not dangerous by itself, but when bundled into a skill described as pure Bilibili research it contributes to hidden capability creep. The main risk is transparency and over-privileging rather than direct exploitation of the compatibility logic.
Version and compatibility checking is not dangerous by itself, but when bundled into a skill described as pure Bilibili research it contributes to hidden capability creep. The main risk is transparency and over-privileging rather than direct exploitation of the compatibility logic.
Version and compatibility checking is not dangerous by itself, but when bundled into a skill described as pure Bilibili research it contributes to hidden capability creep. The main risk is transparency and over-privileging rather than direct exploitation of the compatibility logic.
Version and compatibility checking is not dangerous by itself, but when bundled into a skill described as pure Bilibili research it contributes to hidden capability creep. The main risk is transparency and over-privileging rather than direct exploitation of the compatibility logic.
Version and compatibility checking is not dangerous by itself, but when bundled into a skill described as pure Bilibili research it contributes to hidden capability creep. The main risk is transparency and over-privileging rather than direct exploitation of the compatibility logic.
Version and compatibility checking is not dangerous by itself, but when bundled into a skill described as pure Bilibili research it contributes to hidden capability creep. The main risk is transparency and over-privileging rather than direct exploitation of the compatibility logic.
Version and compatibility checking is not dangerous by itself, but when bundled into a skill described as pure Bilibili research it contributes to hidden capability creep. The main risk is transparency and over-privileging rather than direct exploitation of the compatibility logic.
Version and compatibility checking is not dangerous by itself, but when bundled into a skill described as pure Bilibili research it contributes to hidden capability creep. The main risk is transparency and over-privileging rather than direct exploitation of the compatibility logic.
Detected: suspicious.dangerous_exec, suspicious.dynamic_code_execution