ClawHub

Create and manage a sorted directory structure in AWS S3

Security checks across malware telemetry and agentic risk

Overview

This skill does what it says: it uploads user-selected local files to a user-specified S3 bucket, with ordinary AWS credential and cleanup risks.

Install only if you are comfortable using AWS credentials for S3 uploads. Use a narrowly scoped IAM role or key limited to the intended bucket/prefix, run --dry-run first, verify the source directory does not contain private files, and do not reuse the documentation's staging cleanup pattern with an important directory.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • 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 (2)

Context-Inappropriate Capability

Medium
Confidence
82% confidence
Finding
The bucket access test writes and then deletes an object, requiring delete permissions that are unnecessary for an upload-focused skill. Encouraging deletion broadens the privilege scope and normalizes destructive operations, which can be risky in production buckets or when variables are misconfigured.

Missing User Warnings

Medium
Confidence
84% confidence
Finding
The sync workflow recursively removes the staging directory before and after use with `rm -rf` but does not prominently warn users about the destructive local cleanup. If `STAGING_DIR` is changed, empty, or resolved unexpectedly, this pattern can cause unintended local data loss.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal