ClawHub
Back to skill

Security audit

Guardduty Explainer

Security checks for vulnerabilities and agentic risk

Overview

This is an instruction-only GuardDuty analysis skill that asks users for exported security findings, which is expected for its purpose but should be shared carefully.

Before using this skill, review GuardDuty exports and remove anything not needed for the analysis, such as account IDs, instance IDs, IP addresses, hostnames, bucket or object names, usernames, and other sensitive identifiers. Do not include credentials, access keys, secret keys, or session tokens.

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

Missing User Warnings

Medium
Confidence
94% confidence
Finding
The skill explicitly asks users to paste or export GuardDuty findings, console details, and bulk JSON exports, which commonly contain sensitive account IDs, resource identifiers, IP addresses, hostnames, S3 object details, and incident context. Although it says not to provide credentials, it does not warn users to review and redact sensitive operational data before sharing, creating a real risk of unnecessary exposure of security telemetry and infrastructure details.

Static analysis

No suspicious patterns detected.