Simple Management of Product Documents

• Outcome: Review
• Latest audit: May 29, 2026, 9:28 PM
• Version:
  1.1.0

Overview

The skill is a coherent Feishu document-management guide, but it exposes real-looking Feishu credentials and encourages storing sensitive configuration in shared documents.

Review before installing. Do not use the included Feishu credentials; revoke and rotate them if they belong to you. Use your own least-privilege Feishu app, keep tokens in a secret manager, and store only redacted configuration references in Feishu documents.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (4)

Context-Inappropriate Capability

High

• Confidence: 99% confidence
• Finding: This section exposes what appear to be live Feishu credentials, including an App Secret, user access token, and refresh token, directly in a reference document. Anyone with access to this file could use the tokens immediately and potentially refresh them for continued access, enabling unauthorized document access, modification, or broader compromise of the associated Feishu application and user account.

Missing User Warnings

Medium

• Confidence: 94% confidence
• Finding: The skill explicitly recommends keeping API keys, environment variables, and deployment configuration in a shared Feishu documentation structure, but provides no guidance on secret handling, access control, masking, or use of a proper secret manager. This can lead users to place live credentials into broadly accessible documents, increasing the risk of credential leakage, privilege misuse, and downstream compromise of integrated systems.

Missing User Warnings

High

• Confidence: 99% confidence
• Finding: The document publicly presents real-looking secrets and active OAuth tokens without any warning, masking, or instruction to rotate them. Because these values are directly usable credentials rather than illustrative placeholders, disclosure can lead to immediate unauthorized API access and persistence through token refresh.

Missing User Warnings

Medium

• Confidence: 93% confidence
• Finding: The OAuth response example includes personal data such as a real name and mobile number, creating an unnecessary privacy exposure in addition to token-handling guidance. Even if the tokens in that example were nonfunctional, publishing personal identifiers can facilitate phishing, targeted social engineering, and privacy violations.

VirusTotal

58/58 vendors flagged this skill as clean.