Security audit

Kuaishou Dashi

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 results locally, with no evidence of hidden execution, persistence, privilege escalation, or destructive behavior.

Install only if you are comfortable sending Kuaishou keywords, profile URLs, video URLs, and requested limits to the Guaikei API using your GUAIKEI_API_TOKEN. Review and delete the local logs directory when results may contain business-sensitive research, public comments, account URLs, or analysis outputs you do not want retained on disk.

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
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
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 (17)

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 91% confidence
Finding: The README states that all task results are automatically saved to a local logs/ directory, but it does not clearly warn users that scraped platform data, including comments, account URLs, and analysis outputs, will be written to disk. This creates a real data-handling risk because sensitive or regulated business intelligence can persist locally, be over-retained, or be exposed to other users, backup systems, or malware on the host.
Content: No source excerpt is available for this finding.

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 86% confidence
Finding: This code persists the fetched comment data to disk via log.taskWrite, which is a file-write operation affecting local user data/storage. Although the CLI prints status messages, there is no explicit disclosure here that results will be saved to a file, and no confirmation prompt or comment/docstring warning is present in this file.
Content: No source excerpt is available for this finding.

Context-Inappropriate Capability

Medium

Category: Not specified by scanner
Confidence: 82% confidence
Finding: No manifest is available, so there is no stated purpose or declared scope that would justify sensitive credential access. The code reads process.env.GUAIKEI_API_TOKEN to authenticate external operations, which is a capability with security significance beyond simple local argument processing.
Content: No source excerpt is available for this finding.

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 81% confidence
Finding: The script reads GUAIKEI_API_TOKEN from the environment and uses it together with the user-provided URL in post.createPostTask and post.getPostTask, which are network-facing API calls. This file does not contain a comment, prompt, or user-facing warning that these inputs and credentials will be transmitted to an external service.
Content: No source excerpt is available for this finding.

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 85% confidence
Finding: The script automatically persists fetched results to a local JSON file without user opt-in or any notice in the output contract. Scraped data may contain sensitive or regulated information, and silent persistence increases the risk of unintended retention, disclosure to other local users, or later exfiltration from disk.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium

Category: Not specified by scanner
Confidence: 91% confidence
Finding: This JavaScript file contains natural-language comments, error strings, and help text entirely in Chinese, including user-facing CLI output such as parameter errors and usage/help messages. Because the file does not indicate that the skill is region-specific or provide any user opt-in for language selection, it appears to enforce a specific language/locale in violation of the stated policy.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium

Category: Not specified by scanner
Confidence: 97% confidence
Finding: This code file contains multiple user-facing string literals in Chinese, such as validation and status/error messages. Because the skill does not provide user opt-in, fallback, or any documented justification for enforcing a specific language, it creates a natural-language policy concern under the language/locale rule.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium

Category: Not specified by scanner
Confidence: 94% confidence
Finding: Multiple thrown error messages are written only in Chinese, such as "请求失败", "响应解析失败", and "请求超时", which imposes a specific language on users. The file does not indicate user opt-in for Chinese or justify a locale-specific constraint, so this is a natural-language policy concern.
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 messages at L05, L10, L14, and L18. Because the skill forces a specific language in its natural-language output without any visible opt-in or documented locale limitation in this file, it matches the language/locale policy violation criteria.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 93% confidence
Finding: The package description and keywords are entirely in Chinese, which imposes a specific language choice in user-facing metadata without offering any alternative or opt-in. The policy allows locale constraints only when clearly documented and justified, which is not present here.
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 instructions throughout the file force a single language/locale without offering user opt-in or documenting a justified locale constraint. Under the stated policy, mandating one language without choice can be a language/locale policy violation.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 91% confidence
Finding: This markdown file presents all usage instructions, parameter descriptions, and examples exclusively in Chinese. Under the policy rule, forcing a specific language without user opt-in can be a natural-language policy violation when no alternative language option or justification is provided.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The CLI help and runtime messages in this file are presented only in Chinese, which imposes a specific language on all users without opt-in or documented locale constraints. This matches the policy concern for language/locale restrictions in natural-language content.
Content: No source excerpt is available for this finding.

Missing User Warnings

Low

Category: Not specified by scanner
Confidence: 79% confidence
Finding: This code performs outbound HTTPS GET and POST requests and includes a TOKEN header, while also sending request parameters and JSON payloads to a remote host. Within this file there is no confirmation prompt, logging, comment, or docstring disclosing that user or system data and credentials may be transmitted over the network.
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 hard-coded in Chinese ("重试...次后失败") with no indication that the skill is China-specific or that users can choose their language/locale. This is a natural-language policy issue because it imposes a specific language in a general utility file.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 95% confidence
Finding: This code emits user-facing warning and info strings only in Chinese, which can violate a language/locale policy when no user opt-in or documented regional limitation is present. The file does not indicate that the skill is intentionally China-specific or that alternate locales are supported.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 79% confidence
Finding: The code uses new Date().toLocaleString() in a user-visible log message, which implicitly formats output according to a locale setting the skill does not control or document. In a skill containing Chinese-language user-facing text, this can create inconsistent language/locale behavior without explicit user opt-in or a stated locale policy.
Content: No source excerpt is available for this finding.