finding-twitter-spaces-hosts-by-topic

• Outcome: Pass
• Latest audit: Sep 3, 2026 · 6:37 AM UTC
• Version: 1.0.0

Overview

This skill is a transparent Apify/Twitter scraping workflow, with a notable but manageable API-token handling caveat.

Install only if you are comfortable sending Twitter search queries to Apify and using an Apify API token. Prefer the recommended runner or an authenticated client that keeps the token out of URLs, avoid sensitive search terms, set reasonable maxItems limits, and rotate the token if it appears in logs or shared command output.

SkillSpector

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• MCP Tool Poisoning: Hidden Instructions, Unicode Deception, Parameter Description Injection
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (6)

Description-Behavior Mismatch

Medium

• Confidence: 97% confidence
• Finding: The manifest describes a skill that returns host handles, topic focus, frequency signals, co-host network, and audience size indicators for Twitter Spaces hosts. However, the inputs are generic tweet-scraper parameters such as tweet media filters, replies, mentions, geotags, and quote-tweet filters, which indicate broad tweet retrieval rather than a purpose-built Spaces host discovery workflow.

External Transmission

Medium

• Category: Data Exfiltration

Content

**REST API fallback:**
```bash
curl -X POST \
  "https://api.apify.com/v2/acts/apidojo~tweet-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"searchTerms": ["Twitter Spaces [TOPIC]", "join my Space [TOPIC]", "hosting a Space about [TOPIC]", "upcoming Space [TOPIC]"], "maxItems": 100}'

• Confidence: 87% confidence
• Finding: This command sends user-supplied search terms and an APIFY_TOKEN to an external third-party service. External transmission is expected for this skill, but the token-in-URL pattern is dangerous because URLs are commonly logged by shells, proxies, monitoring systems, and server access logs, creating avoidable credential exposure risk.

External Transmission

Medium

• Category: Data Exfiltration

Content

Wait for `SUCCEEDED`. Fetch dataset:
```bash
curl "https://api.apify.com/v2/actor-runs/$RUN_ID/dataset/items?token=$APIFY_TOKEN"
```

### Step 3: Classify Results

• Confidence: 86% confidence
• Finding: Fetching the dataset from Apify again transmits the APIFY_TOKEN in the URL, repeating the same credential exposure problem during result retrieval. If logs, browser history, terminal history, or intermediary systems capture the URL, the token may be disclosed and reused to access Apify resources.

External Transmission

Medium

• Category: Data Exfiltration

Content

Wait for `SUCCEEDED`. Fetch dataset:
```bash
curl "https://api.apify.com/v2/actor-runs/$RUN_ID/dataset/items?token=$APIFY_TOKEN"
```

### Step 3: Classify Results

• Confidence: 86% confidence
• Finding: Fetching the dataset from Apify again transmits the APIFY_TOKEN in the URL, repeating the same credential exposure problem during result retrieval. If logs, browser history, terminal history, or intermediary systems capture the URL, the token may be disclosed and reused to access Apify resources.

Intent-Code Divergence

Low

• Confidence: 83% confidence
• Finding: The top-level description promises concrete outputs like host handle, Space topic focus, frequency signals, co-host network, and audience size indicators. Later, the output format uses placeholders such as '[Key Field]' and '[Metric 1]' rather than documenting or implementing those promised fields, undermining the claimed intent of the skill.

Missing User Warnings

Low

• Confidence: 88% confidence
• Finding: The skill instructs use of an APIFY_TOKEN but provides no guidance on secure handling, while later examples place the token directly into request URLs. This increases the chance that users will expose the credential through shell history, logs, process listings, analytics, or copied command output.

VirusTotal

64/64 vendors flagged this skill as clean.

Static analysis

No suspicious patterns detected.