Back to skill

Security audit

UAPI 时间戳转换 接口

Security checks for vulnerabilities and agentic risk

Overview

This skill is a narrow UAPI timestamp-conversion helper with disclosed external API use and no local execution, persistence, or hidden data access.

Install this if you want an agent to use UAPI for timestamp conversion. Be aware it may call an external service with the timestamp or date string you provide, and if anonymous quota is exhausted it may suggest creating and using a UAPI key.

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
Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (4)

Vague Triggers

Medium
Confidence
91% confidence
Finding
The trigger keyword 'unixtime' is broad enough to match requests that merely mention Unix timestamps without actually intending to use this specific UAPI endpoint. That can cause the agent to select this skill prematurely and route execution toward an external API call that may be irrelevant to the user's task, increasing the risk of incorrect tool use and unintended data handling.

Natural-Language Policy Violations

Medium
Confidence
87% confidence
Finding
The file’s natural-language instructions and descriptions are entirely in Chinese, and there is no indication that users can opt into another language or that the skill is intentionally restricted to a Chinese-speaking context. Under the policy for natural-language violations, forcing a specific language without user opt-in should be flagged.

Natural-Language Policy Violations

Low
Confidence
80% confidence
Finding
The description hardcodes a bilingual presentation and does not indicate that the user can choose their preferred language or locale. Under the language/locale policy, fixed language behavior without explicit user opt-in can be a policy concern.

Natural-Language Policy Violations

Low
Confidence
79% confidence
Finding
The file presents invocation keywords in both Chinese and English, but it does not state whether the user may choose their preferred language or locale. Under the policy rule, language behavior should either be user-selectable or clearly justified when constrained.

Static analysis

No suspicious patterns detected.