ClawHub
Back to skill

Security audit

traffic-analysis

Security checks for vulnerabilities and agentic risk

Overview

This is a markdown-only analytics guidance skill with no execution, persistence, credential access, or hidden behavior found.

Install only if you want reusable guidance for web analytics, attribution, dark traffic, and UTM reporting. Be aware that its broad trigger terms may make it appear for some general analytics requests, but it does not request sensitive access or perform actions on its own.

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
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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
Findings (2)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The skill’s activation text is broad enough to match many ordinary analytics conversations, which can cause the wrong skill to be invoked outside its intended niche. In an agent system, over-broad routing can lead to irrelevant guidance, context confusion, and accidental overshadowing of more appropriate skills, though it does not directly enable code execution or data exfiltration.

Content

No source excerpt is available for this finding.

YARA rule 'network_reconnaissance': Network reconnaissance and scanning patterns [hacktools]

Medium
Category
YARA Match
Confidence
65% confidence
Finding

YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).

Content

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

md
nattributed visits labeled as "Direct / None"
- **Attribution**: UTM tagging, segmenting, reporting accuracy

## Branded vs. Non-Branded Traffic (Organic)

| Type | Characteristics |
|------|-----------------|
| **Branded** | Higher CTR, conversion, purchase intent; users closer to funnel bottom |
| **Non-branded** | Touchpoint with future users; most sites get more non-brand traffic; competition fiercer |

Brand traffic grows over time as brand awareness increases.

## Bot Traffic

A large share of traffic can be **bot traffic**—RPA, search crawlers, spiders, scrapers. Exclude or segment when evaluating real user behavior; use GA4 filters or segments to isolate human traffic.

## Traffic Channels

| Channel | Typical Sources | Attribution |
|---------|-----------------|-------------|
| **Organic** | Google, Bing, other search | Referrer preserved |
| **Paid (web)** | Google Ads, Meta Ads, etc. | UTM required |
| **Paid (app)** | App install ads; Google App Campaigns, Apple Search Ad

Static analysis

No suspicious patterns detected.