Back to skill

Security audit

Facebook主页帖子批量提取

Security checks for vulnerabilities and agentic risk

Overview

The skill retrieves public Facebook posts through a disclosed API provider and saves results locally, with no evidence of hidden credential collection or unrelated activity.

Use this skill if you are comfortable sharing the requested Facebook page URL with RedFoxHub under your API account. Check the provider's privacy and billing terms, keep the key out of chat and logs, and remember that fetched posts remain in local JSON files and displayed times use UTC+8.

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
  • Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
  • Taint TrackingDirect Taint Flow, Variable-Mediated Taint Flow, Credential Exfiltration Chain
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Findings (6)

Tainted flow: 'req' from os.environ.get (line 57, credential/environment) → urllib.request.urlopen (network output)

Critical
Category
Data Flow
Confidence
90% confidence
Finding

Credentials or environment variables flow to a network sink. This is a high-confidence indicator of credential exfiltration.

Content

Scanner excerpt · scripts/fetch_posts.py (reported line 59)May include surrounding context.

python
data = json.dumps(payload, ensure_ascii=False).encode("utf-8")
    req = urllib.request.Request(API_URL, data=data, headers=headers, method="POST")
    try:
        with urllib.request.urlopen(req, timeout=timeout) as resp:
            return json.loads(resp.read().decode("utf-8"))
    except urllib.error.HTTPError as e:
        body = e.read().decode("utf-8", errors="replace")

All post timestamps are forced to Beijing time (UTC+8) without user opt-in or a justified regional requirement.

Medium
Category
Output Handling
Confidence
92% confidence
Finding

The data notes require publication times to be uniformly converted to Beijing time, imposing a specific locale setting rather than offering a choice. Although this behavior is documented, no regional requirement justifies overriding the user's preferred time zone.

Content

No source excerpt is available for this finding.

Skill declares no tool scope ('permissions' or 'allowed-tools') but code capabilities were detected: env, file_write, network.

Medium
Category
MCP Least Privilege
Confidence
70% confidence
Finding

Without declared permissions the skill's intent is opaque and cannot be validated.

Content

No source excerpt is available for this finding.

The retrieval workflow lacks a disclosure about sharing the requested Facebook profile URL with the third-party API provider.

Medium
Category
Output Handling
Confidence
88% confidence
Finding

The workflow requires a third-party API account but does not explicitly explain that the requested Facebook profile URL will be disclosed to that provider. Although the profile is public and provider involvement is partially apparent, associating a target URL with an authenticated API request can reveal private research interests or account-review activity.

Content

No source excerpt is available for this finding.

Post timestamps are unconditionally converted to Beijing time (UTC+8) without user opt-in or a regional justification.

Low
Category
Output Handling
Confidence
96% confidence
Finding

The skill imposes a fixed regional time zone on displayed timestamps without offering a user choice. Although the conversion is documented, the skill provides no region-specific justification for overriding the user's preferred time zone.

Content

No source excerpt is available for this finding.

Post timestamps are forced into Beijing time without user choice or a documented regional justification.

Low
Category
Output Handling
Confidence
99% confidence
Finding

The field rule explicitly requires converting timestamps to Beijing time (UTC+8). This imposes a locale-specific presentation requirement without user opt-in or a justification tied to the skill's purpose.

Content

No source excerpt is available for this finding.