Back to skill

Security audit

Content Publisher

Security checks for vulnerabilities and agentic risk

Overview

This skill does what it says: it helps publish markdown articles to blogging platforms, but users should treat the publish steps as public-posting actions.

Before installing or using this skill, confirm that any article content is intended for public release, use least-privilege platform tokens, and prefer draft/unpublished modes when testing API publishing commands.

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
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 (2)

Missing User Warnings

Medium
Confidence
94% confidence
Finding
The skill instructs sending full article content and authentication tokens to third-party platforms and enables immediate publication, but it does not include any explicit warning, consent checkpoint, or guidance about the privacy and account risks of doing so. In a publishing skill, external transmission is expected, but failing to disclose that content and credentials will be sent off-system makes accidental data disclosure or unintended posting more likely.

External Transmission

Medium
Category
Data Exfiltration
Content
### 4. Publish to Dev.to (API)
```bash
curl -X POST https://dev.to/api/articles \
  -H "api-key: $DEVTO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
Confidence
85% confidence
Finding
This command performs external transmission of user-provided content to Dev.to using an API key, which creates a real risk of sensitive content leakage or unauthorized publication if the article body contains confidential data or if the action occurs without strong user confirmation. The context makes network transmission functionally necessary for the skill, but the lack of safety controls, redaction guidance, or confirmation before posting increases the danger.

Static analysis

No suspicious patterns detected.