Security audit

testskill-0410zip1

Security checks for vulnerabilities and agentic risk

Overview

This appears to be a real Knot agent editor, but it needs review because it disables normal HTTPS certificate checks while handling credentials and publishing agent changes.

Install only if you trust the publisher and are authorized to administer the target Knot agents. Prefer a version that enables TLS certificate validation or uses a trusted CA bundle before running it with real JWT/API credentials, and treat modify, regenerate, and publish commands as real remote changes.

SkillSpector

Vulnerability Patterns

Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (4)

Lp3

Medium

Category: MCP Least Privilege
Confidence: 86% confidence
Finding: The skill documentation describes Python scripts that use environment data, file input, and networked API access, but the skill declares no permissions or trust boundaries. This creates a capability-transparency problem: users and reviewers may not realize the skill can read local files, access JWT-derived context, and modify/publish remote agent configurations, increasing the risk of misuse or overprivileged execution.

Missing User Warnings

High

Confidence: 99% confidence
Finding: The documentation explicitly instructs clients to disable TLS certificate verification for all requests, which enables man-in-the-middle interception and tampering of API traffic. In this skill, the traffic includes authentication material such as JWT-derived API tokens and privileged agent-management requests, making the risk especially serious.

Missing User Warnings

Medium

Confidence: 99% confidence
Finding: This request sends sensitive authentication data (`jwt_token` and username) over HTTPS while explicitly disabling certificate verification. An attacker able to intercept traffic or spoof DNS/network paths could impersonate the server, capture credentials, and return malicious responses, which is especially dangerous in a skill that manages and publishes agent configurations.

Missing User Warnings

Medium

Confidence: 99% confidence
Finding: The generic POST helper disables TLS verification for every HTTPS request it makes, creating a reusable insecure transport primitive. Because this helper may carry API tokens, agent drafts, system prompts, and publication actions, a network attacker could observe, modify, or replay sensitive management traffic.

Static analysis

Detected: suspicious.insecure_tls_verification

HTTPS certificate verification is disabled.

Warn

Code: suspicious.insecure_tls_verification
Location: scripts/common.py:35