ClawHub
Back to skill

Security audit

Social Media Content Calendar by SocialBu

Security checks for vulnerabilities and agentic risk

Overview

This skill builds social media calendars and optionally schedules posts with clear user authorization.

Planning works without connecting an account. Before enabling SocialBu, review its OAuth permissions and service costs. Scheduling sends your requested content and media to SocialBu and can result in public posts later, so make the intended accounts, copy, and times clear.

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

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
75% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

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

md
2. Call `get_post_options` for those accounts. Check the actual format and media requirements before scheduling each entry. Read `list_posts` for each destination, following pagination, to compare the relevant dates against existing posts. Keep existing posts unless the user authorizes a change.
3. Resolve the final copy, account, actual media, dates/times, and requested state. Do not turn a planning request into a scheduling operation. If these choices are already clear and authorized, proceed without asking for repeated confirmation.
4. Convert each local time to UTC `Y-m-d H:i:s` using the offset on that date. Call `create_post` once per destination with an explicit `post_type: scheduled` and future `scheduled_at`. For saved drafts use `post_type: draft`; for requested team review use `post_type: awaiting_approval`. An existing draft selected for scheduling should use `update_post` with its ID, `post_type: scheduled`, and `scheduled_at`.
5. Supply accessible HTTP(S) media URLs or co

Static analysis

No suspicious patterns detected.