中文 EN

Scan Report

Scan New Files

⚠ Suspicious — Risk Score 45/100
Last scan:23 hr ago Rescan
45 /100
gateway-monitor-installer
Install, update, run, and remove OpenClaw Gateway Monitor + Gateway Watchdog on macOS via LaunchAgent
Skill contains undeclared external network access and reads API credentials from auth profiles to transmit to minimaxi.com, with missing template files referenced in documentation.
Skill Namegateway-monitor-installer
Duration50.1s
Enginepi
⚠
Use with caution
Add explicit declarations for external API calls to minimaxi.com, credential file access to ~/.openclaw/agents/main/agent/auth-profiles.json, and include the missing launchagent plist templates in the package.

Findings 4 items

Severity Finding Location
Medium
Undeclared external network access Doc Mismatch
The gateway-monitor-server.js makes HTTPS requests to https://www.minimaxi.com/v1/api/openplatform/coding_plan/remains without any mention in SKILL.md. This is a hidden network behavior.
MINIMAX_REMAINS_URL = process.env.MINIMAX_REMAINS_URL || 'https://www.minimaxi.com/v1/api/openplatform/coding_plan/remains'
→ Document all external API endpoints in SKILL.md capabilities section
 assets/bin/gateway-monitor-server.js:28
Medium
Undeclared credential file access Sensitive Access
The skill reads the MiniMax API key from ~/.openclaw/agents/main/agent/auth-profiles.json, a sensitive credential storage location, without declaring this access in documentation.
const raw = fs.readFileSync(MINIMAX_AUTH_PROFILE_PATH, 'utf8');
→ Declare access to credential files in SKILL.md or use only environment variables
 assets/bin/gateway-monitor-server.js:309
Medium
Missing launchagent template files Doc Mismatch
SKILL.md and install.sh reference template files at assets/launchagents/*.plist.tpl that do not exist in the package. These files are needed for the installation to succeed.
TPL_MONITOR="$ROOT_DIR/assets/launchagents/${MONITOR_LABEL}.plist.tpl"
→ Include the missing launchagent plist template files in the package
 SKILL.md:24
Low
API key transmitted to external service Data Exfil
The MiniMax API key is sent in the Authorization header to an external service (minimaxi.com). While the service appears legitimate, the transmission of credentials to external endpoints is a sensitive behavior.
Authorization: `Bearer ${keyInfo.key}`
→ Document this behavior explicitly and consider if the API call is necessary for the core functionality
 assets/bin/gateway-monitor-server.js:344
ResourceDeclaredInferredStatusEvidence
Filesystem WRITE READ ✓ Aligned SKILL.md declares file write to ~/.openclaw/tools/
Network NONE READ ✗ Violation gateway-monitor-server.js:28 - external HTTPS call to minimaxi.com not declared
Shell WRITE WRITE ✓ Aligned launchctl commands in install.sh/status.sh are documented
Environment NONE READ ✗ Violation gateway-monitor-server.js:309 - reads MINIMAX_CP_KEY from environment
3 findings
🔗
Medium External URL 外部 URL
http://127.0.0.1:18990
SKILL.md:40
🔗
Medium External URL 外部 URL
https://www.minimaxi.com/v1/api/openplatform/coding_plan/remains
assets/bin/gateway-monitor-server.js:28
🔗
Medium External URL 外部 URL
http://127.0.0.1:18990/api/summary
scripts/status.sh:25

File Tree

6 files · 42.9 KB · 1527 lines
JavaScript 1f · 1321L Shell 4f · 159L Markdown 1f · 47L
├─ ▾ 📁 assets
│ └─ ▾ 📁 bin
│ ├─ 📜 gateway-monitor-server.js JavaScript 1321L · 36.9 KB
│ └─ 🔧 gateway-watchdog.sh Shell 33L · 1.5 KB
├─ ▾ 📁 scripts
│ ├─ 🔧 install.sh Shell 69L · 1.9 KB
│ ├─ 🔧 status.sh Shell 28L · 706 B
│ └─ 🔧 uninstall.sh Shell 29L · 732 B
└─ 📝 SKILL.md Markdown 47L · 1.2 KB

Security Positives

✓ No reverse shell or C2 infrastructure detected
✓ No base64-encoded or obfuscated payloads found
✓ Uses standard macOS LaunchAgent for service management (legitimate)
✓ HTTPS used for external communication (not plaintext)
✓ No credential exfiltration to attacker-controlled infrastructure
✓ Configuration backup mechanism is sensible
✓ Error handling appears robust