T09 · Insecure Skill Coding Practices
- Location
scripts/fb_post.py:30- Finding
Facebook access tokens and application secrets are transmitted through URL query parameters
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This Facebook Page automation skill is not overtly malicious, but it needs review because it can publish or delete Page content while using weak safeguards for powerful access tokens.
Install only if you are comfortable giving the tool a Facebook Page token that can publish and delete content. Prefer environment variables or a secret manager over `fb_config.json`, avoid never-expiring production tokens when possible, rotate/revoke tokens if exposed, and manually confirm any delete or reschedule target before running commands.
scripts/fb_post.py:30Facebook access tokens and application secrets are transmitted through URL query parameters
scripts/fb_post.py:19Long-lived privileged Page token is stored in an unprotected plaintext project file
SKILL.md:22Runtime dependency installation is unpinned and lacks integrity verification
The skill claims support for comment, reply, and comment deletion, but the analysis indicates those capabilities are not actually implemented. This mismatch can mislead users and orchestrators into trusting the skill for moderation actions that will not occur, causing unsafe automation decisions, failed workflows, or incorrect assumptions about content state.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Cách lấy Facebook Page Access Token
## Tổng quan
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Cách lấy Facebook Page Access Token
## Tổng quan
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Cách lấy Facebook Page Access Token
## Tổng quan
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Cách lấy Facebook Page Access Token
## Tổng quan
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Cách lấy Facebook Page Access Token
## Tổng quan
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
---
## Bước 2: Lấy User Access Token tạm thời (để test)
1. Vào **[Graph API Explorer](https://developers.facebook.com/tools/explorer/)**
2. Chọn app của bạn ở dropdown
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
---
## Bước 2: Lấy User Access Token tạm thời (để test)
1. Vào **[Graph API Explorer](https://developers.facebook.com/tools/explorer/)**
2. Chọn app của bạn ở dropdown
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
---
## Bước 2: Lấy User Access Token tạm thời (để test)
1. Vào **[Graph API Explorer](https://developers.facebook.com/tools/explorer/)**
2. Chọn app của bạn ở dropdown
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
---
## Bước 2: Lấy User Access Token tạm thời (để test)
1. Vào **[Graph API Explorer](https://developers.facebook.com/tools/explorer/)**
2. Chọn app của bạn ở dropdown
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
---
## Bước 2: Lấy User Access Token tạm thời (để test)
1. Vào **[Graph API Explorer](https://developers.facebook.com/tools/explorer/)**
2. Chọn app của bạn ở dropdown
This section explicitly guides creation of a long-lived or non-expiring Page Access Token. Such tokens materially increase the blast radius and persistence of any local compromise or accidental disclosure, because an attacker who obtains the token may retain page-management access for an extended period without needing to reauthenticate.
---
## Bước 4: Tạo Long-Lived Page Access Token (không hết hạn)
Page Access Token từ bước 3 thường **không hết hạn** nếu page đã publish và app đã qua review cơ bản.
Stating that the Page Access Token can 'không hết hạn' ('never expires') normalizes use of persistent credentials without balancing security considerations. In a skill that automates posting and comment management, compromise of such a token enables durable unauthorized actions on the Facebook Page, making the operational context more dangerous.
## Bước 4: Tạo Long-Lived Page Access Token (không hết hạn)
Page Access Token từ bước 3 thường **không hết hạn** nếu page đã publish và app đã qua review cơ bản.
Để chắc chắn, đổi sang long-lived token:
The skill documents networked actions against Facebook Graph API and handling of local config/token material, but it does not declare any explicit tool scope such as allowed tools or permissions. That creates a governance gap: an agent may invoke network or environment-capable execution without clear sandboxing or review boundaries, increasing the chance of unintended external actions or secret exposure.
The trigger language is very broad, covering nearly any request related to posting or managing Facebook Page content. Over-broad invocation criteria can cause the skill to activate for ambiguous user requests, leading to unintended posting, scheduling, or destructive content-management actions in an external account.
The skill documents post deletion commands without warning that the action is destructive or advising a confirmation step. In the context of a Facebook Page management skill, this is more dangerous because the action affects public-facing content and may be irreversible or difficult to recover.
Comment deletion is presented as a simple command with no indication of irreversible impact, audit requirements, or confirmation. Because this skill manages public engagement on a Facebook Page, accidental or unauthorized comment removal can damage trust, moderation integrity, and recordkeeping.
The manifest explicitly advertises destructive actions such as deleting comments and deleting scheduled posts, but it does not disclose any confirmation flow, permission scoping, audit logging, or user-warning safeguards. In a social-media automation skill, these capabilities can be abused or triggered accidentally to remove content or community interactions, causing reputational harm and operational disruption for the Facebook Page.
This markdown file documents deletion capabilities for posts and comments, but it does not include any warning that these actions are destructive or may be irreversible. Under the markdown-file criteria for missing user warnings, descriptions that affect user data or system integrity should disclose such risks.
The document instructs users to store a long-lived Facebook Page access token in a local JSON file, but only warns against committing it to Git. That omits important local-secret risks such as plaintext storage, accidental inclusion in backups, exposure via shared machines, permissive filesystem permissions, or leakage through logs and tooling; because the token may not expire, compromise can enable persistent unauthorized page management.
The manifest description explicitly advertises comment management capabilities such as commenting on posts, replying to comments, and deleting comments. In this file, there are no functions or CLI commands interacting with Facebook comment endpoints; the implemented behavior is limited to page post creation and scheduled post management.
Many docstrings, help strings, examples, and runtime messages are presented only in Vietnamese, which imposes a specific language on users without opt-in. The file does not state that the tool is intentionally limited to Vietnamese-speaking users or provide an alternative locale.
The delete command performs destructive actions immediately against the Facebook Graph API with no confirmation prompt, dry-run mode, or additional guardrails. In an agent skill that may be invoked from natural-language workflows, this increases the chance of accidental or unauthorized content deletion if the wrong post ID is passed or a user request is misinterpreted.
The skill's manifest description and user-facing documentation are entirely in Vietnamese, which can impose a language constraint on users without explicit opt-in. The file does not state that the skill is intentionally region-specific or offer an alternative language option.
Most of the natural-language content in this reference is written in Vietnamese, with no indication that the skill supports other languages or that Vietnamese is a justified locale requirement. The policy calls for flagging language or locale constraints when they are imposed without user opt-in or documented justification.