Back to skill

Security audit

score-report

Security checks for vulnerabilities and agentic risk

Overview

The skill is mostly a coherent SEO reporting helper, but it tells agents to run an unbundled local validator from a discovered skills root before using evidence.

Install only if you trust the separately installed Groundcrew doctor script and understand which local skills root will be used. Before relying on the skill, verify the validator path, avoid passing sensitive evidence records to unknown local scripts, and use only already configured read-only connectors or explicitly approved paid API batches.

Vulnerability Patterns
  • Tool Hijacking and SpoofingModifies or replaces tools so legitimate-looking calls execute attacker logic
  • 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 (1)

T07 · Tool Hijacking and Spoofing

Error
Location
SKILL.md:7
Finding

Execution of an Unverified External Tool from a Discoverable Skills Root

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, line 7
Vulnerability Type: T07: Skill Instruction Hijacking and Spoofing
Risk Level: High

Vulnerable code snippet:

markdown
Read `references/provider-selection.md` before choosing a source. Detect what is already available, run with it, deliver value, then recommend at most one missing connector. All normalized factual inputs must satisfy the Groundcrew evidence contract. Locate the active skills root and run `<skills-root>/.groundcrew/groundcrew-doctor.py --evidence <record.json>` before using them in a conclusion.

Technical Analysis

The skill directs the agent to discover an “active skills root” and execute .groundcrew/groundcrew-doctor.py from that location. This executable is not included in the audited project and is not constrained by an exact trusted path, pinned cryptographic digest, signature, or other integrity verification.

Consequently, the effective code executed by this instruction depends on mutable local state outside the reviewed package. A malicious or compromised component capable of writing to the selected skills root could place or replace the expected script with attacker-controlled Python code. The file would retain the appearance and path of a legitimate validation tool while executing arbitrary behavior.

Passing <record.json> to the unverified program also exposes that evidence file to the external process. If the evidence contains sensitive business, analytics, site, or customer information, malicious code could read and disclose it. Exploitability requires the attacker to control or modify the discovered skills root, influence its resolution, or compromise the component that provisions the external validator.

Attack Path

  1. An attacker obtains write access to a candidate active skills root or influences which directory is resolved as that root.
  2. The attacker creates or replaces .groundcrew/groundcrew-doctor.py with mali ...[truncated 1225 chars]
Remediation
View remediation

Remediation Suggestions

  1. Bundle the validator inside the audited skill package so that the reviewed artifact contains the exact code that will execute.
  2. Resolve the validator from a fixed package-relative path rather than searching for an active skills root.
  3. Verify the validator against a pinned cryptographic digest or trusted signature immediately before execution.
  4. Refuse execution when the resolved script is a symbolic link, is outside the approved package directory, has unexpected ownership or permissions, or fails integrity verification.
  5. Invoke the interpreter with an argument array rather than constructing a shell command. Treat the evidence path as an opaque argument and validate that it points to an expected regular file.
  6. Run validation in a restricted subprocess with minimum filesystem access, a sanitized environment, no inherited secrets, and network access disabled unless explicitly required.
  7. If an external validator remains necessary, display its resolved absolute path and integrity identity and require explicit user approval before first execution.
  8. Document the validator’s trusted source, versioning process, expected permissions, and update mechanism so that replacements are auditable.
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

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/connectors.md (reported line 48)May include surrounding context.

md
- **Tier 1.** Google Suggest for expansion (unofficial endpoint; treat as hints, `confidence: low`). A SERP the user pastes or fetches is an observation for that query, locale, device, and date — record all four.
- **DataForSEO.** Paid, per-request. Read `dataforseo.md`; show the cost preflight and get approval for each batch.
- **Ahrefs MCP** (`https://api.ahrefs.com/mcp/mcp`, API key on a plan that includes MCP) and **Semrush MCP** (`https://mcp.semrush.com/v1/mcp`, OAuth or API key). Use only when the user already pays for the tool and has configured the MCP in their client. Label rows `source: "ahrefs"` / `"semrush"`, `confidence` per the vendor's own accuracy notes; these are third-party estimates, not the user's own data.
- **TrustGrowth.** `keywords` (typed opportunities with volume, difficulty, intent, current position, scores) for the verified site. SERP snapshots per keyword are scheduled (TEC-7796).

### `~~link database` — backlinks and authority