other
- Location
SKILL.md:29- Finding
Unrestricted Recurring System and Network Reconnaissance
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 29-41
Vulnerability Type: Excessive environment reconnaissance
Risk Level: LowCode Snippet
The following is an English translation of the relevant source instructions:
text 1. Periodic checks (every N minutes) 2. Check: - Disk utilization - Memory utilization - CPU load - Network status - Process status 3. Detect anomalies - Threshold exceeded? → Proactively alert 4. Report - Normal: concise report - Abnormal: detailed explanation and recommendationsTechnical Analysis
The skill directs an agent to perform recurring inspection of network and process state without defining an authorized target, collection boundaries, redaction requirements, or retention policy. Process details may disclose service names, command-line arguments, software versions, security tools, or sensitive file paths. Network inspection may expose listening services, active connections, internal addresses, and deployment topology.
The declared tool list contains only
read, so the package does not itself implement network or process enumeration. Exploitation therefore depends on the hosting agent granting additional system-observation or command-execution capabilities. The issue is an overbroad instruction rather than embedded executable malware.Attack Path
- A user or automated trigger activates the monitoring skill.
- The agent interprets the periodic monitoring workflow as authorization to inspect network and process state.
- If the host exposes suitable tools, the agent enumerates processes, services, connections, or related operating-system information.
- Sensitive operational details enter the agent context.
- The details are reproduced in health reports or anomaly alerts and may be exposed to unintended recipients.
Impact Assessment
The issue does not independently grant additional operating-syst ...[truncated 391 chars]
- Remediation
View remediation
Remediation Suggestions
- Require explicit user authorization before inspecting process or network state.
- Define an allowlist of hosts, processes, interfaces, and metrics that may be monitored.
- Collect aggregate health metrics instead of full process arguments or connection details.
- Redact credentials, tokens, query parameters, internal addresses, usernames, and sensitive paths from reports.
- Define report recipients, retention periods, and access controls.
- Prohibit inspection of unrelated users, containers, namespaces, or hosts.
- Align the documented workflow with the declared
read-only tool capability.
