ClawHub
Back to skill

Security audit

Expanso log-sanitize

Security checks for vulnerabilities and agentic risk

Overview

This log-sanitizing skill is coherent and not malicious, but it should be reviewed because it handles secrets, exposes an unauthenticated HTTP endpoint on all interfaces, and its redaction rules can miss common secret formats.

Install only if you understand its limits: use the CLI mode or bind the MCP service to localhost, avoid exposing the HTTP endpoint to a network without authentication and request limits, and do not rely on this as a complete sanitizer for JSON, quoted, multiline, or unusual credential formats.

A.I.G

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

Error
Location
pipeline-cli.yaml:30
Finding

Incomplete Redaction Patterns Can Leak Sensitive Credentials

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
pipeline-mcp.yaml:15
Finding

Unauthenticated HTTP Sanitization Service Listens on All Network Interfaces

Content
View full analysis
Remediation
View remediation

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (3)

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

Scanner excerpt · README.md (reported line 29)May include surrounding context.

PORT=8080 expanso-edge run pipeline-mcp.yaml &

Make request

curl -X POST http://localhost:8080/sanitize
-H "Content-Type: application/json"
-d '{"log": "password=secret123 api_key=sk-123abc"}'

text

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

Scanner excerpt · pipeline-mcp.yaml (reported line 6)May include surrounding context.

yaml
#
# Usage:
#   PORT=8080 expanso-edge run pipeline-mcp.yaml &
#   curl -X POST http://localhost:8080/sanitize \
#     -d '{"log": "password=secret123 token=abc123"}'
#
# No API key needed - runs entirely locally.

Vague Triggers

Low
Category
Not specified by scanner
Confidence
88% confidence
Finding

The pipeline exposes an HTTP server on 0.0.0.0 with no authentication, and the endpoint accepts arbitrary POST data for processing. Even though the function is local log sanitization, binding to all interfaces makes the service reachable from other hosts and can enable unauthorized use, data exposure to the service, or abuse for denial of service via large or frequent requests.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.