安全决策报告

complianceradar-ai-monitor

Documentation-only skill with no implementation code but exhibits suspicious branding ('empire-skills') and placeholder API keys that could be mistaken for real configuration.

安装决策优先 来源: 手动上传 扫描时间: 2026/4/5
文件 1
IOC 9
越权项 0
发现 4
最直接的威胁证据
高危 API 密钥
API_KEY="your-sec-api-key"

为什么得出这个结论

1/4 个维度触发
通过
声明与实际能力

声明资源与推断能力基本一致。

阻止
隐藏执行与外联

提取到 3 个高危 IOC 或外联信号。

通过
攻击链与高危发现

没有形成明确的恶意路径。

复核
依赖与供应链卫生

没有完整依赖信息,供应链判断需要保留弹性。

风险分是怎么被拉高的

Suspicious branding reference +15

Homepage links to 'github.com/ncreighton/empire-skills' - 'empire' in security context often references post-exploitation frameworks

Hardcoded placeholder API keys +12

Lines 116, 119, 132 contain example API keys in configuration format that could be copy-pasted as real credentials

No implementation code +10

Skill describes capabilities but contains zero scripts or code - cannot verify security claims made in documentation

Unverifiable security claims +5

Claims 'API keys never logged or transmitted' but no code exists to verify this behavior

最关键的证据

中危 文档欺骗

Suspicious 'empire-skills' branding

The homepage references 'github.com/ncreighton/empire-skills'. The term 'empire' in security contexts often references post-exploitation frameworks. This branding choice is unusual for a compliance monitoring tool and warrants verification.

SKILL.md:4
Verify this repository is legitimate. Cross-reference with official sources before trusting this skill.
中危 文档欺骗

Placeholder API keys in example configuration

Lines 116, 119, and 132 contain API key placeholders (e.g., 'your-sec-api-key') in a format that resembles real configuration. While clearly intended as examples, users may copy-paste these as actual credentials.

SKILL.md:116
Use clearly marked placeholder syntax like '<YOUR_SEC_API_KEY>' or 'INSERT_YOUR_KEY_HERE' to prevent accidental credential misconfiguration.
中危 文档欺骗

Unverifiable security claims

The documentation makes security claims ('API keys never logged or transmitted to third parties') without any implementation code to verify. This is classic doc-to-code mismatch - the behavior cannot be audited.

SKILL.md:249
Since no code exists, these claims cannot be verified. Request or verify actual implementation code before trusting security guarantees.
低危 供应链

No implementation code present

This SKILL.md describes capabilities but contains zero executable code, scripts, or implementation files. The skill cannot function as documented.

SKILL.md:1
Confirm the actual implementation exists in the referenced repository before use. This may be an incomplete or placeholder skill.

声明能力 vs 实际能力

文件系统 通过
声明 NONE
推断 NONE
No file operations present - documentation only
网络访问 通过
声明 READ
推断 NONE
_meta declares curl/jq binaries but no implementation code exists to verify network calls
命令执行 通过
声明 NONE
推断 NONE
No shell execution code present
环境变量 通过
声明 READ
推断 NONE
_meta declares env vars but no code reads them - can't verify actual usage

可疑产物与外联

高危 API 密钥
API_KEY="your-sec-api-key"

SKILL.md:116

高危 API 密钥
API_KEY="your-fda-api-key"

SKILL.md:119

高危 API 密钥
API_KEY="your-google-api-key"

SKILL.md:132

中危 外部 URL
https://www.sec.gov/cgi-bin/browse-edgar

SKILL.md:115

中危 外部 URL
https://open.fda.gov/

SKILL.md:118

中危 外部 URL
https://hooks.slack.com/services/YOUR/WEBHOOK/URL

SKILL.md:125

中危 外部 URL
https://www.sec.gov/cgi-bin/browse-edgar.

SKILL.md:314

中危 外部 URL
https://api.fda.gov/status.json

SKILL.md:320

提示 邮箱
[email protected]

SKILL.md:384

依赖与供应链

没有结构化依赖告警。

文件构成

1 个文件 · 387 行
Markdown 1 个文件 · 387 行
需关注文件 · 1
SKILL.md Markdown · 387 行
Suspicious 'empire-skills' branding · Placeholder API keys in example configuration · Unverifiable security claims · No implementation code present · API_KEY="your-sec-api-key" · API_KEY="your-fda-api-key" · API_KEY="your-google-api-key" · https://www.sec.gov/cgi-bin/browse-edgar · https://open.fda.gov/ · https://hooks.slack.com/services/YOUR/WEBHOOK/URL · https://www.sec.gov/cgi-bin/browse-edgar. · https://api.fda.gov/status.json · [email protected]

安全亮点

No executable code present - cannot perform malicious actions without additional implementation
No base64-encoded payloads or obfuscated commands detected
No credential exfiltration mechanisms present
No network requests to suspicious IPs or domains
No sensitive path access patterns detected