ClawHub
Back to skill

Security audit

proxymock

Security checks for vulnerabilities and agentic risk

Overview

This proxymock skill is coherent and not malicious, but it deserves Review because it can capture, persist, replay, and upload real API or database traffic without enough safety framing around sensitive data.

Install only if you expect the agent to use proxymock for traffic capture and replay. Treat generated RRPair files, logs, and snapshots as potentially sensitive; avoid production traffic unless authorized, sanitize recordings before sharing or uploading, be careful with cloud push, and do not use TLS bypass examples outside isolated local testing.

A.I.G

Vulnerability Patterns
  • 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
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (6)

Missing User Warnings

High
Category
Not specified by scanner
Confidence
97% confidence
Finding

The documentation promotes recording real API and database traffic but does not warn that captured requests and responses may contain credentials, session tokens, PII, secrets, or regulated data. Because the skill is specifically designed to intercept and persist live traffic into RRPair files, the context makes this especially dangerous: it can create durable local artifacts containing sensitive production data with no safety guidance.

Content

No source excerpt is available for this finding.

Missing User Warnings

High
Category
Not specified by scanner
Confidence
98% confidence
Finding

The documented proxymock cloud push snapshot command can send recorded snapshots to an external service, but the skill gives no warning that those snapshots may include captured API/database payloads, credentials, or other confidential material. Given the skill's traffic-capture purpose, uploading without explicit disclosure and consent materially raises exfiltration risk.

Content

No source excerpt is available for this finding.

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
87% confidence
Finding

The documentation explicitly recommends curl -k, which disables TLS certificate verification and trains users to bypass transport security checks. Even though this is framed as local proxymock testing, copy-pasted use of -k against non-local or sensitive environments can enable man-in-the-middle attacks and mask certificate problems that should be investigated.

Content

Scanner excerpt · references/language-reference.md (reported line 36)May include surrounding context.

proxymock record -- java -Dhttp.proxyHost=localhost -Dhttp.proxyPort=4140 -jar app.jar

text

### cURL Testing
```bash
curl -k -x http://localhost:4140 https://api.example.com/endpoint

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
89% confidence
Finding

The skill clearly enables network-affecting operations through the proxymock CLI, including proxying, replaying traffic, cloud upload, and MCP server startup, yet it declares no explicit tool scope or permission boundaries. In an agent setting, that omission increases the chance the skill is invoked with broader-than-necessary authority, allowing unintended outbound connections, traffic interception, or service interaction.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The activation criteria are very broad, covering generic testing, traffic replay, CI integration, and any task involving proxymock or Speedscale traffic replay. In an automated agent environment, this can cause over-triggering, where the skill is selected for loosely related requests and then performs traffic-capturing or network-interacting actions the user did not specifically intend.

Content

No source excerpt is available for this finding.

External Transmission

Medium
Category
Data Exfiltration
Confidence
50% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · references/language-reference.md (reported line 38)May include surrounding context.

cURL Testing

bash
curl -k -x http://localhost:4140 https://api.example.com/endpoint

The -k flag trusts proxymock's TLS cert. The -x flag routes through the proxy.

Static analysis

No suspicious patterns detected.