ClawHub
Back to skill

Security audit

Instagram API

Security checks for vulnerabilities and agentic risk

Overview

This skill is a read-only guide for using a third-party Instagram data API, with privacy and credential-handling cautions users should understand before use.

Install only if you are comfortable sending Instagram query targets and a fetcher.sh API key or x402 payment to instagram.fetcher.sh. Use it for authorized, privacy-respecting access to public data, protect the Bearer key, and avoid collecting or retaining follower, story, comment, or location data beyond what you actually need.

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
  • 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 (4)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

The skill explicitly enables access to potentially sensitive Instagram data including followers, followings, stories, comments, hashtag/location feeds, and influencer/competitor monitoring, but it does not warn users about privacy, consent, platform-policy, or lawful-use considerations. In an agent setting, this omission can normalize bulk surveillance or profiling use cases and increase the chance that users invoke the capability without understanding the sensitivity of the data being retrieved.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
81% confidence
Finding

This markdown file documents endpoints for profiles, followers, followings, stories, posts, and comments, which can expose user and social-graph data, but it provides no warning about privacy or responsible handling of returned data. Under the markdown-file criteria for SQP-2, descriptions should warn when behavior could affect user data, privacy, or system integrity.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The examples encourage sending a live Bearer API key and potentially sensitive Instagram query targets to a third-party service without any warning about data disclosure, retention, or trust boundaries. In a skill intended for API usage, this omission can lead users to unknowingly transmit credentials and target data to an external provider, increasing the risk of credential misuse, privacy issues, or unintended data sharing.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
77% confidence
Finding

This markdown file instructs users how to retrieve follower lists and export them to CSV, which can affect user privacy and data handling, but it does not include any caution about handling personal data responsibly. Under the markdown-specific warning criterion, descriptions of behaviors affecting privacy should disclose that risk.

Content

No source excerpt is available for this finding.

Static analysis

Detected: suspicious.exposed_secret_literal

File appears to expose a hardcoded API secret or token.

Critical
Code
suspicious.exposed_secret_literal
Location
references/scenarios.md:11

File appears to expose a hardcoded API secret or token.

Critical
Code
suspicious.exposed_secret_literal
Location
SKILL.md:71