Back to skill

Security audit

living-contract-diff

Security checks for vulnerabilities and agentic risk

Overview

ClawScan rates this skill benign with high confidence: the completed scans found one install-command pattern, which the verdict treats as a note rather than evidence of harmful behavior.

The scan covered the single Markdown component completely, and the other completed checks reported no issues. The install instructions point to a GitHub-hosted package; consider whether you trust that source before installing. Benign is not a guarantee of zero risk.

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
Vulnerability Patterns
  • YARA SignaturesMalware Match, Webshell Match, Cryptominer Match
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (1)

YARA rule 'agent_skill_remote_bootstrap_execution': Remote script or code download followed by execution/bootstrap installation [agent_skills]

High
Category
YARA Match
Confidence
85% confidence
Finding

YARA rule matched a known malware signature (reverse shell, backdoor, ransomware, C2 framework, or info stealer).

Content

Scanner excerpt · SKILL.md (reported line 24)May include surrounding context.

spec. observe reads a HAR file and writes a baseline of statistics only — presence counts, type unions, nullability — never payload values (one designed exception: fields with at most 20 distinct values store those candidate values, because they are the contract). diff compares a baseline with the spec and reports drift. Nothing from a HAR or a spec is ever executed.

Install

bash
pip install git+https://github.com/RakTikoo/living-contract-diff
# or, isolated, with pipx:
pipx install git+https://github.com/RakTikoo/living-contract-diff

With uv:

bash
uv tool install git+https://github.com/RakTikoo/living-contract-diff

This provides the lcdiff command (standard library only).

Run

Build a baseline from recorded traffic, then diff it against the spec:

bash
lcdiff observe --har traffic.har --out baseline.json
lcdiff diff --baseline baseline.json --spec openapi.json

Machine-readable report: add --format json to diff. The spec may be YAML (`.y