Security audit

LurkAPI: Demand research

Security checks for vulnerabilities and agentic risk

Overview

The skill performs clearly described market research through LurkAPI, with ordinary privacy and API-credit considerations.

Use search terms and URLs you are comfortable sharing with LurkAPI, and agree on a credit budget. Its [privacy policy](https://lurkapi.com/privacy) says request parameters are logged for 14 days and the account's first request is retained with the account. Keep the API key out of chat. The complete bundled artifact was reviewed; remote service behavior was not audited.

A.I.G

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

SkillSpector

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
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)

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 · SKILL.md (reported line 18)May include surrounding context.
Without MCP (Codex, Cursor, scripts), every tool is GET https://api.lurkapi.com plus its path, with the same params as a query string (URL-encoded) and the key from LURKAPI_API_KEY in the x-api-key header:

bash
curl -s "https://api.lurkapi.com/v1/tiktok/profile?handle=nike" -H "x-api-key: $LURKAPI_API_KEY"

If LURKAPI_API_KEY isn't set but LURKAPI_KEY is (the name older docs used), use that. Raw answers are big: pipe them through jq to keep the fields you need. No key yet? Ask the user to create one at https://lurkapi.com/dashboard (100 free credits on sign-up, then a balance below 25 tops back up to 25 every day) and to set LURKAPI_API_KEY in their shell. Never ask for the key in the chat, and never print it.

The research workflow sends user-provided product ideas and search terms to LurkAPI without a privacy warning.

Medium

Category: Output Handling
Confidence: 93% confidence
Finding: The workflow instructs the agent to submit the user's seed and related queries to external APIs. Although the API provider and costs are documented, the skill never warns that potentially confidential product ideas or business research terms will leave the user's environment.
Content: No source excerpt is available for this finding.