ClawHub
Back to skill

Security audit

PosteAhora is a tool to schedule and publish social media posts to Instagram, TikTok, YouTube, X (Twitter), Facebook, LinkedIn, Threads, Bluesky and Discord — from your own code, terminal, CI, or an AI agent, via a CLI, an MCP server, or a REST API.

Security checks across malware telemetry and agentic risk

Overview

This is a disclosed social media publishing helper with real account-posting risk, but its capabilities match its purpose and include reasonable user-control guardrails.

Install only if you want an agent to operate PosteAhora-connected social accounts. Prefer drafts or scheduled posts for review, confirm every live post and target account, assume uploaded media URLs may be public, and keep the API key out of screenshots, logs, shell history, and shared config files.

SkillSpector

By NVIDIA
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 (3)

Missing User Warnings

Medium
Confidence
92% confidence
Finding
The quick-start instructs users to pass an API key directly on the command line using `posteahora auth --key pah_live_xxxxxxxx`. Secrets entered this way are commonly exposed through shell history, process listings, terminal recordings, and shared documentation snippets, which can lead to account compromise if a real key is used. In a publishing CLI context, the key likely grants access to connected social accounts, making accidental disclosure more consequential.

Missing User Warnings

Low
Confidence
89% confidence
Finding
The README instructs users to store a live API key in ~/.posteahora/config.json but does not warn that the key is a sensitive credential or recommend file-permission hygiene and secret-handling practices. In an AI-agent, shared workstation, or CI context, this increases the chance of accidental credential exposure via logs, backups, dotfile syncing, or overly broad filesystem access.

Missing User Warnings

Medium
Confidence
93% confidence
Finding
The README describes uploading media and publishing posts but does not clearly warn that uploaded media may become publicly accessible and that publishing can trigger irreversible external side effects on real social accounts. In an agentic setting, unclear safety boundaries can lead to unintended public disclosure, reputational harm, or accidental posting to production accounts.

VirusTotal

54/54 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

Detected: suspicious.exposed_secret_literal

File appears to expose a hardcoded API secret or token.

Critical
Code
suspicious.exposed_secret_literal
Location
README.md:84