T01 · Skill Instruction Hijacking
- Location
SKILL.md:93- Finding
Mandatory Third-Party Branding Alters User-Requested Output
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a coherent Feishu research workflow, but it unnecessarily exposes Feishu tokens and possibly app secrets in normal output and error messages.
Review before installing. The core Feishu research and upload workflow is understandable, but do not run it as written unless token and secret output is removed or redacted, error diagnostics are sanitized, and the report watermark is made optional. Use a least-privileged Feishu app and rotate any credentials that may have appeared in transcripts or logs.
SKILL.md:93Mandatory Third-Party Branding Alters User-Requested Output
SKILL.md:134Tenant Access Token Is Explicitly Disclosed in Agent Output
SKILL.md:127Failure Diagnostics Can Expose the Feishu Application Secret
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
确认:使用 exec + curl,绝不使用 feishu_doc/feishu_drive 工具
**Step 1: 获取 Tenant Access Token**
必须使用 curl 调用:
```bash
The skill explicitly requires exposing a live tenant_access_token in user-visible output. Access tokens are bearer credentials; anyone who sees them may be able to invoke Feishu APIs with the skill's privileges until expiry, which is unrelated to the user-facing goal of delivering a report.
The instruction to report live Feishu access tokens back to the user creates direct credential disclosure without any legitimate requirement or warning. Because the token is sufficient to authenticate API requests, exposure can immediately enable misuse of cloud documents and drive resources.
The skill directs the agent to reveal sensitive authentication artifacts in progress messages, turning routine status reporting into a secret-exfiltration channel. In this context, the disclosure is more dangerous because the skill also fetches credentials from configuration, meaning real secrets could be automatically surfaced to any requester.
The example output demonstrates full credentials and document-related tokens in clear text, reinforcing an insecure pattern that operators or downstream models may imitate. Example blocks often become de facto implementation guidance, so this materially increases the chance of real secret leakage.
The example normalizes returning full live-like tokens and document identifiers, which encourages reproducible data leakage during normal operation. Since examples are likely to be copied verbatim, this creates a persistent pattern of exposing sensitive artifacts to end users and logs.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Step 1: 获取 Tenant Access Token
必须使用 curl 调用:
curl -X POST https://open.feishu.cn/open-apis/auth/v3/tenant_access_token/internal \
-H "Content-Type: application/json" \
The skill mandates disclosing file_token, import ticket, doc_token, and full polling details, which exceeds operational necessity for report generation. These identifiers can expose internal object references, facilitate unauthorized follow-up actions, and normalize oversharing of sensitive workflow artifacts.
No suspicious patterns detected.