扫描报告
20 /100
openclaw-grok-search
Cross-platform real-time web research and search via an OpenAI-compatible Grok endpoint
Legitimate web research tool with minor documentation gap - subprocess usage for interactive config setup is not explicitly declared but is described in Quick Start documentation.
可以安装
Consider adding 'subprocess' to allowed-tools mapping in SKILL.md if shell execution capability is intended. Otherwise no security concerns.
安全发现 2 项
| 严重性 | 安全发现 | 位置 |
|---|---|---|
| 低危 | Subprocess execution not declared in allowed-tools 文档欺骗 | scripts/grok_search.py:85 |
| 低危 | Config file with API key present in package 敏感访问 | config.json:2 |
| 资源类型 | 声明权限 | 推断权限 | 状态 | 证据 |
|---|---|---|---|---|
| 网络访问 | READ | READ | ✓ 一致 | urllib.request.Request POST to Grok endpoint |
| 命令执行 | NONE | WRITE | ✓ 一致 | scripts/grok_search.py:85 - subprocess.run([sys.executable, configure_path]) |
| 文件系统 | NONE | READ | ✓ 一致 | config.json reading via _load_json_file |
| 文件系统 | NONE | WRITE | ✓ 一致 | scripts/configure.py:65 - write_text to config.json |
5 项发现
中危 外部 URL 外部 URL
https://your-grok-endpoint.example README.md:84 中危 外部 URL 外部 URL
https://ai.huan666.de/register?aff=eB8Z README.md:114 中危 外部 URL 外部 URL
https://linux.do/t/topic/1627339 README.md:120 中危 外部 URL 外部 URL
https://ai.huan666.de config.json:2 提示 邮箱 邮箱地址
[email protected] README.md:149 目录结构
6 文件 · 24.3 KB · 789 行 Python 2f · 551L
Markdown 2f · 220L
JSON 2f · 18L
├─
▾
scripts
│ ├─
configure.py
Python
│ └─
grok_search.py
Python
├─
config.example.json
JSON
├─
config.json
⚠
JSON
├─
README.md
Markdown
└─
SKILL.md
Markdown
依赖分析 1 项
| 包名 | 版本 | 来源 | 已知漏洞 | 备注 |
|---|---|---|---|---|
None (standard library only) | N/A | stdlib | 否 | No external dependencies |
安全亮点
✓ No credential harvesting - API key is user-provided configuration
✓ No data exfiltration - all network traffic is to the configured Grok endpoint only
✓ No obfuscation - all code is readable plaintext Python
✓ No reverse shell or C2 infrastructure
✓ No hidden instructions in comments or documentation
✓ No supply chain risks - only standard library dependencies used
✓ HTTP behavior matches documentation (OpenAI-compatible API calls)