Back to skill

Security audit

TweetAPI

Security checks for vulnerabilities and agentic risk

Overview

This skill provides clearly bounded public Twitter/X lookups, with appropriate credential protections and quota controls.

TweetAPI is a third-party service that receives your lookup requests and consumes API quota. Review its [privacy policy](https://tweetapi.com/privacy), approve only read-only MCP access, and keep application API keys server-side. Never provide Twitter/X passwords, cookies, or session tokens.

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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
80% 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 · references/hosted-mcp.md (reported line 57)May include surrounding context.

md
## Handle authorization failures

If OAuth fails, direct the user to the TweetAPI dashboard and agent integration guide. Do not ask the user to paste an API key, Twitter cookie, password, token, or session value into the chat.

If the client does not support remote OAuth MCP servers, use a server-side REST integration. Do not put credentials in prompts or client configuration.

External Transmission

Medium
Category
Data Exfiltration
Confidence
50% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · references/integration.md (reported line 16)May include surrounding context.

md
throw new Error("TWEETAPI_API_KEY is not configured");
}

const url = new URL("https://api.tweetapi.com/tw-v2/user/by-username");
url.searchParams.set("username", username);

const response = await fetch(url, {

Static analysis

No suspicious patterns detected.