Back to skill

Security audit

system-time

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward MCP time utility with visible Chinese-language output and no evidence of hidden data access, persistence, exfiltration, or destructive behavior.

Install this only if Chinese-language tool text is acceptable for your workflow. For stronger supply-chain control, prefer a release that pins dependency versions and includes a lockfile.

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
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (9)

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill description, feature explanations, and example invocations are entirely in Chinese, including examples that instruct users to request output in Chinese formats. This indicates a language-specific experience without any stated user opt-in, alternative language support, or justification for restricting the skill to Chinese-language usage.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The code forces the 'zh-CN' locale in time formatting and returns all tool descriptions and output text in Chinese, including localized weekday/month names and error messages. This is a natural-language policy concern because the skill does not provide any user opt-in or language/locale selection, and no region-specific justification is present in the file.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

This TypeScript skill forces the Chinese locale in multiple user-facing paths, including toLocaleString('zh-CN') and Chinese-only output strings and weekday/month labels. The policy for natural-language violations applies to all file types, and there is no visible user choice or documented opt-in for language/locale selection.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
89% confidence
Finding

The natural-language content throughout the skill documentation is presented exclusively in Chinese, including the description, examples, and parameter explanations. Under the policy, forcing a specific language without user opt-in can be a locale/language policy violation unless the constraint is explicitly 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
95% confidence
Finding

The package description is written only in Chinese ("获取系统当前时间的 MCP Skill"), which imposes a specific language in user-facing metadata without indicating user opt-in or a documented locale-specific purpose. This can violate language/locale policy when the skill is otherwise general-purpose and not clearly scoped to a Chinese-only audience.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
93% confidence
Finding

The runtime dependency '@modelcontextprotocol/sdk' is specified with a caret range, allowing newer minor/patch releases to be installed without explicit review. In security-sensitive agent skills, this weakens supply-chain control and can unexpectedly pull in vulnerable or behavior-changing versions, especially given known advisories exist for this package family.

Content

Scanner excerpt · package.json (reported line 24)May include surrounding context.

json
"author": "Your Name",
  "license": "MIT",
  "dependencies": {
    "@modelcontextprotocol/sdk": "^0.5.0"
  },
  "devDependencies": {
    "@types/node": "^20.0.0",

Unverifiable Dependency: @modelcontextprotocol/sdk has 3 known advisory(ies) (CVE-2026-25536 (@modelcontextprotocol/sdk has cross-client data leak via shared server/transport); CVE-2026-0621 (Anthropic's MCP TypeScript SDK has a ReDoS vulnerability); CVE-2025-66414 (Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protec)), but the manifest does not pin a version, so it is unknown whether the installed release is affected

Low
Category
Supply Chain
Confidence
95% confidence
Finding

The manifest uses '@modelcontextprotocol/sdk' without pinning to a specific version, while that package has multiple known advisories. Because the exact installed version is not constrained here, consumers may resolve to an affected release, exposing the skill to issues such as data leakage, ReDoS, or DNS rebinding-related weaknesses depending on deployment context.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
40% confidence
Finding

Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.

Content

Scanner excerpt · package.json (reported line 27)May include surrounding context.

json
"@modelcontextprotocol/sdk": "^0.5.0"
  },
  "devDependencies": {
    "@types/node": "^20.0.0",
    "typescript": "^5.0.0"
  }
}

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
40% confidence
Finding

Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.

Content

Scanner excerpt · package.json (reported line 28)May include surrounding context.

json
},
  "devDependencies": {
    "@types/node": "^20.0.0",
    "typescript": "^5.0.0"
  }
}

Static analysis

No suspicious patterns detected.