Security audit

Guaikei Kuaishou Creator Finder

Security checks for vulnerabilities and agentic risk

Overview

This skill is a disclosed Kuaishou public-data lookup tool that uses a third-party API token and saves query results locally, with no evidence of account posting, hidden execution, or persistence beyond logs.

Install only if you are comfortable sending Kuaishou search terms or URLs to guaikei.com with your GUAIKEI_API_TOKEN. Review or delete the generated logs directory if queries, comments, or result data should not remain in the workspace.

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
Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access

Findings (24)

Description-Behavior Mismatch

Medium

Category: Not specified by scanner
Confidence: 91% confidence
Finding: The package metadata markets the skill as a passive analytics/discovery tool, but the exposed CLI entry points also support posting and commenting. This mismatch can mislead reviewers and users about the skill’s real capabilities, increasing the chance that an agent or operator grants it broader trust or execution than intended; in a social-platform context, write actions can enable spam, unwanted engagement, or account misuse.
Content: No source excerpt is available for this finding.

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 93% confidence
Finding: The script writes the full comment results and request metadata to a local JSON file automatically, with no opt-in, path selection, redaction, or warning to the user. This can expose potentially sensitive scraped content and activity history to other local users, backups, or unintended sharing, especially on multi-user systems or in CI/workspaces.
Content: No source excerpt is available for this finding.

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 90% confidence
Finding: This code persists the full task output to disk via log.taskWrite, but there is no nearby confirmation prompt or explicit user-facing warning that the fetched data will be saved as a local file. Although the script logs progress and prints output, it does not clearly disclose the file-write side effect before performing it.
Content: No source excerpt is available for this finding.

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 92% confidence
Finding: The CLI persists search results to a local JSON file named with user-controlled content (the keyword) without an explicit runtime warning or consent prompt. This creates a privacy and data-handling risk because potentially sensitive search terms and returned content are stored on disk by default, where they may be exposed to other local users, backups, or later collection processes.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: This file hard-codes Chinese natural-language strings in comments, thrown errors, and help text, such as the module description and parameter descriptions. Under the stated policy, forcing a specific language without user opt-in is a natural-language policy violation unless the locale restriction is explicitly justified, which is not present here.
Content: No source excerpt is available for this finding.

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 84% confidence
Finding: This code performs outbound HTTPS GET and POST requests and includes a TOKEN header, which means user or system data may be transmitted to an external service. The file contains no confirmation prompt, user-visible logging, or explanatory comment/docstring disclosing this network behavior or credential use.
Content: No source excerpt is available for this finding.

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 80% confidence
Finding: The functions require a token and then place it into the TOKEN HTTP header for outbound requests. Although the code validates that a token string is present, it does not include any user-facing notice, comment, or docstring explaining that credentials are being used and transmitted.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium

Category: Not specified by scanner
Confidence: 96% confidence
Finding: This JavaScript file contains multiple user-facing error strings in Chinese, such as the validation errors printed at lines L05, L10, L14, L18, L23, L50, L54, L59, and L64. Under the policy, forcing a specific language without user opt-in or documented justification is a natural-language policy violation.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 87% confidence
Finding: The skill title and primary user-facing description are presented only in Chinese, and the document does not state that users may interact in other languages or choose their preferred locale. Under the policy for natural-language violations, forcing a specific language without opt-in can be problematic unless a locale restriction is explicitly documented and justified.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 87% confidence
Finding: The natural-language description forces a single language/locale experience in the package metadata and does not offer any user language choice or state that the skill is intentionally region-specific. Under the stated policy, language constraints should either be optional for users or clearly documented and justified.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 92% confidence
Finding: The README forces a single language/locale for all user-facing instructions and support information. Under the policy, language restrictions should either offer a user choice or be clearly justified as region-specific; this file does neither explicitly.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 79% confidence
Finding: The entire changelog is presented only in Chinese, and there is no indication that users may choose another language or that the skill is intentionally limited to a Chinese-speaking or region-specific context. Under the stated policy, forcing a specific language without opt-in can be a natural-language policy violation.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 92% confidence
Finding: This markdown file presents all user-facing instructions, parameter descriptions, and examples exclusively in Chinese. Under the policy rule for language or locale constraints, this can be a natural-language policy violation because the skill implicitly forces a specific language without indicating user choice or justified region-specific scope.
Content: No source excerpt is available for this finding.

Missing User Warnings

Low

Category: Not specified by scanner
Confidence: 77% confidence
Finding: The function sends the provided URL to a remote API and authenticates with a token, which involves transmitting user-supplied and credential-related data over the network. In this file, there is no confirmation prompt, warning comment, or user-facing disclosure explaining that this data is being sent externally.
Content: No source excerpt is available for this finding.

Missing User Warnings

Low

Category: Not specified by scanner
Confidence: 75% confidence
Finding: This code performs an authenticated HTTP request containing the URL and limit parameters to retrieve comment-task information from an external endpoint. The file includes retry error logs, but no warning, prompt, or explanatory comment that would disclose this data transmission to users.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The CLI help text, validation errors, and status messages are presented entirely in Chinese, with no apparent option to select another language or locale. This can violate language/locale policy when a skill imposes a specific language without user opt-in or documented regional scope.
Content: No source excerpt is available for this finding.

Missing User Warnings

Low

Category: Not specified by scanner
Confidence: 85% confidence
Finding: The script reads a sensitive environment variable via process.env.GUAIKEI_API_TOKEN to authenticate API requests, but this file does not provide a user-facing warning, prompt, or explanatory comment about credential usage. For code files, access to sensitive environment variables should have some visible disclosure unless clearly documented elsewhere.
Content: No source excerpt is available for this finding.

Missing User Warnings

Low

Category: Not specified by scanner
Confidence: 80% confidence
Finding: The script reads process.env.GUAIKEI_API_TOKEN to authenticate requests, which is access to sensitive credential material. In this file there is no visible warning, comment, or help text informing the user that the command depends on and consumes an environment-stored API token.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 88% confidence
Finding: User-visible help text and status messages are consistently presented in Chinese, which imposes a specific language on all users. The file does not offer a language selection mechanism or document that the skill is intentionally limited to a Chinese-speaking context.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 92% confidence
Finding: The user-facing error strings are hard-coded in Chinese, and the success/error output throughout this utility appears to assume a Chinese-language user. For a general-purpose logging utility, this is a locale policy concern because no opt-in, fallback, or justification is provided for restricting output to a single language.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 94% confidence
Finding: Multiple user-visible error strings are hard-coded in Chinese, such as 请求失败, 响应解析失败, and token guidance text. This enforces a specific language without any opt-in, fallback, or documented justification, which violates the language/locale policy criteria.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The thrown error string is hardcoded in Chinese (重试${maxAttempts}次后失败), which imposes a specific language in user-visible text. The file does not offer any language choice or document a justified locale-specific constraint, so this is a natural-language policy violation.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 89% confidence
Finding: This file contains user-facing warning and info strings only in Chinese, which imposes a specific language/locale on users without any visible opt-in or alternative. The policy for natural-language violations applies to all file types, including code string literals.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 93% confidence
Finding: The module contains user-facing Chinese text in both the header comment and the printed banner, including the visible product name shown to users. This appears to enforce a specific language/locale without offering a user choice or documenting that the skill is intentionally region-specific, which matches the language/locale policy concern.
Content: No source excerpt is available for this finding.