ClawHub
Back to skill

Security audit

Analytics Tracking

Security checks for vulnerabilities and agentic risk

Overview

This is a markdown-only analytics guidance skill with disclosed tracking examples and no executable install, persistence, or hidden behavior.

Use this skill for analytics and conversion-tracking work, but review privacy requirements before implementing its examples. Avoid sending PII, secrets, raw payment details, or unnecessary persistent identifiers to analytics or ad platforms, and gate analytics/marketing tags behind appropriate consent where required.

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
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (7)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill trigger is overly broad because it claims applicability whenever a user asks how to know if something is working, which can capture many unrelated requests outside analytics and measurement. This can cause incorrect skill invocation, leading the agent to apply tracking-oriented guidance in inappropriate contexts, increasing the chance of misrouting, bad advice, or unintended access to contextual files for tasks the user did not actually request.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The eval explicitly expects the skill to trigger on casual phrasing like 'our tracking seems broken' without defining boundaries for when the analytics-tracking skill should or should not activate. This can cause over-broad routing, where unrelated debugging, product, or engineering requests are incorrectly handled by this skill, leading to misclassification and potentially inappropriate guidance in user workflows.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

This reference encourages collection of extensive telemetry, including user identifiers, referrers, error messages, account metadata, and payment-adjacent events, but provides no guidance on data minimization, consent, retention, PII avoidance, or regulatory compliance. In an analytics-tracking skill, users may implement these examples directly, which increases the chance of over-collection or accidental capture of sensitive personal or financial data.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The reference includes examples that send user_id and user properties such as user_type and plan_name to GA4/GTM without any accompanying privacy, consent, or data-minimization guidance. In an analytics implementation skill, readers are likely to copy these snippets directly, which can lead to collection of persistent identifiers or potentially sensitive profiling data without proper legal basis, consent handling, or policy review.

Content

No source excerpt is available for this finding.

Unsafe Defaults

Medium
Category
Tool Misuse
Confidence
60% confidence
Finding

Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.

Content

Scanner excerpt · references/ga4-implementation.md (reported line 229)May include surrounding context.

md
### DebugView

Enable with:
- URL parameter: `?debug_mode=true`
- Chrome extension: GA Debugger
- gtag: `'debug_mode': true` in config

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

This markdown file demonstrates collecting user-level data (userId, userType) and later sending analytics and advertising events to third parties such as GA4 and Facebook Pixel, but it does not explicitly warn readers about privacy implications or the need to avoid transmitting personal data. Because SQP-2 applies to markdown files when descriptions omit warnings about behaviors affecting user data or privacy, this is a meaningful omission.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
90% confidence
Finding

The example loads https://connect.facebook.net/en_US/fbevents.js, which hardcodes a specific locale in the natural-language-facing configuration. Under SQP-3, forcing a specific language or locale without user opt-in or documented justification is a policy concern.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.