扫描报告
20 /100
message-hub
Message Hub - AI Team Message Hub Client for async collaboration
A legitimate message-hub Python client that uses network requests for hub communication, with minor documentation gaps (undeclared network permission, example API keys in docs) but no malicious behavior detected.
可以安装
Declare network:READ in SKILL.md allowed-tools if the skill is intended to use the requests library. Replace example API key placeholders in README.md with clearly-labeled placeholder strings. Fix the syntax error in hub_client.py line 211.
安全发现 3 项
| 严重性 | 安全发现 | 位置 |
|---|---|---|
| 低危 | Undeclared network resource usage 文档欺骗 | hub_client.py:77 |
| 低危 | Example API key patterns in documentation 文档欺骗 | README.md:29 |
| 低危 | Syntax error prevents CLI from running 代码执行 | hub_client.py:211 |
| 资源类型 | 声明权限 | 推断权限 | 状态 | 证据 |
|---|---|---|---|---|
| 网络访问 | NONE | READ | ✓ 一致 | hub_client.py:77 — self.session.request(method, url, json=data, timeout=30) |
| 文件系统 | NONE | NONE | — | No file read/write operations in code |
| 命令执行 | NONE | NONE | — | No shell command execution |
| 环境变量 | NONE | READ | ✓ 一致 | hub_client.py:54 — os.getenv reads MESSAGE_HUB_URL, MESSAGE_HUB_API_KEY, MESSAGE… |
3 高危 3 项发现
高危 API 密钥 疑似硬编码凭证
API_KEY="sk_xb_xxxxxxxxxxxxxxxx" README.md:29 高危 API 密钥 疑似硬编码凭证
api_key="sk_xb_xxxxxxxxxxxxxxxx" README.md:47 高危 API 密钥 疑似硬编码凭证
api_key="sk_xj_xxxxxxxxxxxxxxxx" README.md:134 目录结构
4 文件 · 26.4 KB · 891 行 Python 2f · 576L
Markdown 2f · 315L
├─
hub_client.py
Python
├─
message_hub.py
Python
├─
README.md
Markdown
└─
SKILL.md
Markdown
依赖分析 1 项
| 包名 | 版本 | 来源 | 已知漏洞 | 备注 |
|---|---|---|---|---|
requests | * | pip | 否 | Version not pinned; requests is used for core network functionality (legitimate) |
安全亮点
✓ No shell execution, no subprocess calls, no os.system or popen usage
✓ No credential harvesting or environment variable enumeration for exfiltration
✓ No base64 encoding, obfuscation, or eval/atob patterns
✓ No sensitive file access (~/.ssh, ~/.aws, .env reading for theft)
✓ No curl|bash, wget|sh, or remote script execution
✓ No reverse shell, C2, or data exfiltration endpoints
✓ No hidden HTML instructions or prompt injection payloads
✓ HMAC signature uses API key legitimately for message authentication only
✓ API key is used only for X-API-Key header, not transmitted to third parties
✓ requests library version is unpinned but has no known critical vulnerabilities at time of analysis