T09 · Insecure Skill Coding Practices
Error
- Location
templates/narodmon_config.json:2- Finding
Narodmon Credentials and Sensor Data Transmitted over Unencrypted HTTP
- Content
View full analysis
- Remediation
View remediation
Security audit
Narodmon Telegram Summary
Security checks for vulnerabilities and agentic risk
Overview
The skill does what it says, but its default setup sends Narodmon credentials and private sensor access material over unencrypted HTTP.
Review before installing. Use HTTPS or an encrypted tunnel for authenticated Narodmon access, especially for private sensors, and avoid running the cron job until the endpoint is changed or validated. Store the config with restrictive permissions, keep it out of version control, and change the output path from shared /tmp to a private directory.
Vulnerability Patterns
- Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
- Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
- Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
- Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
- Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (2)
T09 · Insecure Skill Coding Practices
Warning
- Location
scripts/narodmon_daily.py:216- Finding
Predictable Shared Temporary File Allows Symlink-Based File Overwrite
- Content
View full analysis
- Remediation
View remediation
Vulnerability Patterns
- Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
- Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
- MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
- Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
- Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (7)
Undeclared Tool Scope
Medium
- Category
- MCP Least Privilege
- Confidence
- 92% confidence
- Finding
The skill instructs use of network access, shell scripts, and cron execution but does not declare any explicit tool scope or permissions boundaries. In agent environments, this increases the chance of overbroad execution or accidental misuse because consumers cannot easily tell what capabilities the skill expects or should be restricted to.
- Content
Missing User Warnings
Medium
- Category
- Not specified by scanner
- Confidence
- 99% confidence
- Finding
The documentation explicitly states that HTTP is acceptable for private sensors even though the password-derived authentication hash and API traffic travel unencrypted. This enables interception or replay by anyone on the network path and materially weakens confidentiality for account credentials and sensor data.
- Content
Sudo/Root Execution
Medium
- Category
- Privilege Escalation
- Confidence
- 80% confidence
- Finding
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
- Content
md 7. **Cron script path.** Hermes `no_agent` cron scripts must be relative filenames in the Hermes scripts directory — not absolute paths. Use a `.sh` wrapper that calls the Python script with full paths. 8. **Config file permissions.** The JSON config contains credentials in plaintext. Restrict file permissions (`chmod 600 narodmon_config.json`). Do not commit to version control. 9. **`sensorsHistory` accepts both `id` and `sensors`.** Use `sensors` array for multiple sensors in one request. Response has `sensors[]` (metadata) and `data[]` (time-value pairs with sensor `id` field for matching).
Sudo/Root Execution
Medium
- Category
- Privilege Escalation
- Confidence
- 80% confidence
- Finding
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
- Content
md 7. **Cron script path.** Hermes `no_agent` cron scripts must be relative filenames in the Hermes scripts directory — not absolute paths. Use a `.sh` wrapper that calls the Python script with full paths. 8. **Config file permissions.** The JSON config contains credentials in plaintext. Restrict file permissions (`chmod 600 narodmon_config.json`). Do not commit to version control. 9. **`sensorsHistory` accepts both `id` and `sensors`.** Use `sensors` array for multiple sensors in one request. Response has `sensors[]` (metadata) and `data[]` (time-value pairs with sensor `id` field for matching).
External Transmission
Medium
- Category
- Data Exfiltration
- Confidence
- 60% confidence
- Finding
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- Content
python f"Content-Type: {mime}\r\n\r\n" ).encode("utf-8") + file_data + f"\r\n--{boundary}--\r\n".encode("utf-8") url = f"https://api.telegram.org/bot{token}/sendPhoto" req = urllib.request.Request(url, data=body, headers={"Content-Type": f"multipart/form-data; boundary={boundary}"}, method="POST")
Natural-Language Policy Violations
Medium
- Category
- Not specified by scanner
- Confidence
- 95% confidence
- Finding
The configuration hard-codes "lang": "ru", which imposes a specific language/locale setting. Under the policy, locale restrictions should either offer user choice or be clearly documented and justified as region-specific.
- Content
Natural-Language Policy Violations
Low
- Category
- Not specified by scanner
- Confidence
- 94% confidence
- Finding
The file includes natural-language comments entirely in Russian ('запуск через venv Hermes', 'Поместить...'), which imposes a specific language context without any user choice. Under the stated policy, locale/language constraints should be optional or justified; here no such justification or opt-in is present.
- Content
Static analysis
No suspicious patterns detected.