Back to skill

Security audit

Apify Bluesky Scraper

Security checks for vulnerabilities and agentic risk

Overview

The skill is coherent for Bluesky searches through Apify, but it needs Review because it handles an Apify credential in request URLs and does not clearly warn users that search data is sent to Apify.

Install only if you are comfortable sending Bluesky search terms and requested limits to Apify under your Apify account. Use a minimally scoped token if possible, avoid shell tracing or logging full commands, and prefer revising the skill to use Authorization headers instead of token query parameters before use.

Vulnerability Patterns
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • 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
Findings (1)

T09 · Insecure Skill Coding Practices

Warning
Location
SKILL.md:28
Finding

Apify API Token Exposed in URL Query Parameters

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (9)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

The invocation description says to use the skill when the user asks to 'search Bluesky, find Bluesky posts, monitor Bluesky discussions, or extract Bluesky data.' Several of these phrases are broad and the file does not provide exclusion conditions or narrower trigger constraints, which could cause the skill to activate on loosely related requests.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill instructs the agent to send user-provided search terms and retrieve data through a third-party service, but it does not explicitly warn the user that their query will be transmitted to Apify. This creates a privacy and consent risk, especially if users provide sensitive topics, names, or investigative queries expecting only local processing.

Content

No source excerpt is available for this finding.

External Transmission

Medium
Category
Data Exfiltration
Confidence
91% confidence
Finding

The hardcoded use of the Apify API endpoint confirms that data leaves the local environment and is processed by a third party. In this skill context that transmission is expected, but it is still security-relevant because there is no explicit warning, no consent gate, and the token is passed in a way that may be exposed in logs.

Content

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

Step 2: Run the Actor (synchronous)

bash
RESULT=$(curl -s -X POST "https://api.apify.com/v2/acts/WAJfBnZBYR9mJrk5d/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"searchTerms": ["SEARCH_TERM"], "maxResults": 50, "sortBy": "relevance"}')
echo "$RESULT" | jq '.'

External Transmission

Medium
Category
Data Exfiltration
Confidence
91% confidence
Finding

The hardcoded use of the Apify API endpoint confirms that data leaves the local environment and is processed by a third party. In this skill context that transmission is expected, but it is still security-relevant because there is no explicit warning, no consent gate, and the token is passed in a way that may be exposed in logs.

Content

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

Step 2: Run the Actor (synchronous)

bash
RESULT=$(curl -s -X POST "https://api.apify.com/v2/acts/WAJfBnZBYR9mJrk5d/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"searchTerms": ["SEARCH_TERM"], "maxResults": 50, "sortBy": "relevance"}')
echo "$RESULT" | jq '.'

External Transmission

Medium
Category
Data Exfiltration
Confidence
91% confidence
Finding

This external endpoint initiates an Apify actor run and therefore transfers user input and account-authenticated activity to a third-party platform. The skill context makes the transmission functionally necessary, but the absence of privacy notice and the use of token-in-URL make it a genuine security weakness rather than a pure false positive.

Content

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

For larger jobs (async):

bash
RUN_ID=$(curl -s -X POST "https://api.apify.com/v2/acts/WAJfBnZBYR9mJrk5d/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"searchTerms": ["TERM"], "maxResults": 50}' | jq -r '.data.id')

External Transmission

Medium
Category
Data Exfiltration
Confidence
91% confidence
Finding

This external endpoint initiates an Apify actor run and therefore transfers user input and account-authenticated activity to a third-party platform. The skill context makes the transmission functionally necessary, but the absence of privacy notice and the use of token-in-URL make it a genuine security weakness rather than a pure false positive.

Content

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

For larger jobs (async):

bash
RUN_ID=$(curl -s -X POST "https://api.apify.com/v2/acts/WAJfBnZBYR9mJrk5d/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"searchTerms": ["TERM"], "maxResults": 50}' | jq -r '.data.id')

External Transmission

Medium
Category
Data Exfiltration
Confidence
84% confidence
Finding

Polling the external run status does not itself add much new user-data exposure beyond the original submission, but it continues authenticated communication with Apify using a token in the URL. The main concern is credential handling and undisclosed ongoing interaction with the third-party service.

Content

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

Step 3: Poll and fetch (if async)

bash
STATUS=$(curl -s "https://api.apify.com/v2/actor-runs/$RUN_ID?token=$APIFY_TOKEN" | jq -r '.data.status')
# Poll every 5s until SUCCEEDED or FAILED
curl -s "https://api.apify.com/v2/actor-runs/$RUN_ID/dataset/items?token=$APIFY_TOKEN" | jq '.'

External Transmission

Medium
Category
Data Exfiltration
Confidence
90% confidence
Finding

Fetching dataset items from Apify retrieves externally processed results and continues authenticated third-party data exchange. If the scraped results or the user’s original query are sensitive, this extends the privacy exposure surface, especially with query-string token usage and no explicit user notice.

Content

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

bash
STATUS=$(curl -s "https://api.apify.com/v2/actor-runs/$RUN_ID?token=$APIFY_TOKEN" | jq -r '.data.status')
# Poll every 5s until SUCCEEDED or FAILED
curl -s "https://api.apify.com/v2/actor-runs/$RUN_ID/dataset/items?token=$APIFY_TOKEN" | jq '.'

Step 4: Present results

External Transmission

Medium
Category
Data Exfiltration
Confidence
82% confidence
Finding

The log retrieval endpoint continues external authenticated access and may expose operational details in third-party logs. While lower impact than the initial data submission, it still reflects insecure credential handling and undisclosed external interactions within the skill.

Content

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

md
## Error Handling
- If APIFY_TOKEN not set: `export APIFY_TOKEN=your_token`
- If run FAILS: `curl -s "https://api.apify.com/v2/actor-runs/$RUN_ID/log?token=$APIFY_TOKEN"`
- Rate limited (429): wait 60s, retry