ClawHub
Back to skill

Security audit

ab-test-analyzer

Security checks for vulnerabilities and agentic risk

Overview

The skill is a minimal A/B test analyzer instruction file with no bundled executable code, but it is under-documented around invocation scope and API key handling.

Before installing, confirm where scripts/ab_test_analyzer.py comes from, what service AB_API_KEY authenticates to, and whether experiment data will be sent externally. Store the API key securely and avoid pasting it into shared files or logs.

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
  • 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 (2)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The skill's invocation cues are very broad ('testing related functionality', 'ab tasks', 'analytics operations'), which can cause the agent to select this skill in contexts far beyond narrowly scoped A/B test analysis. Over-broad routing increases the chance of unnecessary execution, unintended access to configured secrets, or misuse of downstream scripts against inputs the skill was not designed to handle.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

The documentation requires an API key via environment variable but provides no warning about secret sensitivity, storage, rotation, logging, or output handling. In an agent setting, this can normalize insecure credential practices and increase the risk that the key is exposed through shell history, debug output, shared environments, or improperly scoped execution contexts.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.