ClawHub
Back to skill

Security audit

iii-functions-triggers

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-only skill for implementing iii engine functions and triggers, with no hidden execution, persistence, credential handling, or unrelated authority.

Before installing, users should understand this skill guides agents to create iii engine functions and triggers such as HTTP, cron, queue, state, stream, and subscription bindings. Review generated code for the intended engine, trigger paths, schedules, and side effects, but the skill itself does not perform those actions automatically.

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

Vague Triggers

Low
Category
Not specified by scanner
Confidence
88% confidence
Finding

The 'When to Use' section says to use the skill when a task is primarily about the skill and when the request 'directly asks for this pattern or an equivalent implementation.' The phrase 'equivalent implementation' is open-ended and could overlap with many general function, event, or serverless requests, making activation boundaries less precise despite the later boundary notes.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.