vision-support
Audited by Socket on Aug 6, 2026
4 alerts found:
Anomalyx3SecurityOverall, the code is primarily a CLI for vision-model inference and configuration. It does not show explicit malware behaviors (no eval/command execution for payloads, no backdoors, no exfiltration of system secrets). The biggest security concern is that it detects/provisions an HTTP(S) proxy and then globally overrides fetch to tunnel HTTPS via CONNECT + TLS, which can redirect all HTTPS traffic through a proxy and could facilitate interception if the proxy URL/config is compromised. Separately, loading remote image URLs without an allowlist introduces SSRF risk in threat models where untrusted users can provide image URLs.
该技能目的与主要能力大体一致,未见明显恶意下载执行链或无关越权访问;但它依赖未验证的本地脚本处理 API Key,并明确支持把图片与密钥转发到任意自定义 OpenAI 兼容 endpoint。整体更像高敏感度的桥接集成而非恶意技能,结论为 SUSPICIOUS:主要风险来自第三方/自定义数据路由、凭据转交和敏感图片外传。
This shell fragment itself shows no explicit malware behavior (no credential theft, exfiltration, persistence, or obvious obfuscated payloads). However, it is a supply-chain execution installer: it clones an unpinned remote GitHub repository and then (optionally) executes a Node.js initialization script from the downloaded/copied contents. The lack of integrity pinning (commit/tag/checksum/signature) is the primary security concern. Additionally, rm -rf introduces operational risk if an unintended --dir is used. Overall risk is moderate and hinges on upstream repository integrity and what vision.mjs does.
This package will execute a local postinstall script during npm install. That behavior is common for setup tasks but also allows potentially malicious activities (data exfiltration, installing git hooks, running external downloads, modifying files, spawning shells). You should inspect the contents of bin/postinstall.mjs (and any scripts it calls, such as install.mjs or install.sh) before installing or run the install in a sandboxed environment. No explicit high-risk indicators (like http:// URLs or registry overrides) appear in package.json itself, but executing arbitrary local JS at install time is a non-trivial security risk if the package is untrusted.