Back to skill

Security audit

JSON工具箱(专业版)

Security checks for vulnerabilities and agentic risk

Overview

This JSON helper is not clearly malicious, but it asks for broad file, command, API, and administrator-style authority that is wider than its stated JSON-processing purpose.

Review this skill before installing. It may be useful as a JSON reference, but do not let it run commands, install packages, call external APIs, or rerun operations as administrator unless you have checked the exact command, dependency, files, credentials, and destination service.

Vulnerability Patterns
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • 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
Findings (2)

T08 · Insecure Dependencies

Warning
Location
SKILL.md:188
Finding

Unpinned Third-Party Dependency Installation

Content
View full analysis

Vulnerability Details

File Location: SKILL.md:188
Vulnerability Type: Unverified and unpinned package installation
Risk Level: Medium

Vulnerable code snippet:

markdown
| flatted (optional) | Library | Optional | `npm install flatted` or `pip install flatted`, for circular references |

Technical Analysis

The Skill recommends installing flatted through npm or pip without specifying an exact version, lockfile, integrity hash, trusted registry, or package-verification procedure. Package names and mutable version ranges are resolved at installation time, meaning the installed artifact can differ from the artifact originally reviewed.

The command is also ambiguous about the package ecosystem. Packages with the same name in different registries are not necessarily maintained by the same publisher or implemented from the same source.

Package installations can execute lifecycle or build code with the privileges of the Agent process. Consequently, compromise of a package, registry account, distribution channel, or similarly named package could convert this instruction into arbitrary local code execution.

Attack Path

  1. A user asks the Agent to process JSON containing circular references.
  2. The Agent follows the dependency guidance in SKILL.md.
  3. It runs npm install flatted or pip install flatted without a pinned version or integrity verification.
  4. The package manager resolves the currently available artifact from its configured registry.
  5. A compromised, substituted, or malicious artifact executes installation-time code or is imported during later processing.
  6. The artifact operates with the permissions available to the Agent or user account.

Impact Assessment

Successful exploitation could permit arbitrary code execution with the Agent process's privileges. Depending on those privileges, the affected package could read or modify accessible project files, environment var ...[truncated 283 chars]

Remediation
View remediation

Remediation Suggestions

  1. Identify the intended package ecosystem explicitly and do not present npm and pip packages as interchangeable.
  2. Pin a reviewed package version, such as an exact semantic version rather than the latest available release.
  3. Commit and enforce an ecosystem-specific lockfile.
  4. Verify package integrity using a trusted checksum, signature, or lockfile integrity field.
  5. Restrict installation to the official expected registry and verify the publisher and repository.
  6. Run dependency installation without administrative privileges and in an isolated environment.
  7. Use the documented built-in WeakSet implementation when replacing circular references with markers is sufficient, avoiding the dependency entirely.
  8. Add dependency vulnerability and provenance checks to the review or CI process.

T05 · Unauthorized Access and Privilege Escalation

Warning
Location
SKILL.md:337
Finding

Blanket Recommendation to Rerun Operations with Administrator Privileges

Content
View full analysis

Vulnerability Details

File Location: SKILL.md:337 and duplicate guidance at SKILL.md:377
Vulnerability Type: Unnecessary privilege escalation
Risk Level: Medium

Vulnerable code snippet, faithfully rendered in English:

markdown
| Insufficient permissions | The current user lacks read/write permissions | Check file permissions and run as administrator |

The same troubleshooting instruction is repeated at lines 337 and 377.

Technical Analysis

The troubleshooting guidance recommends running as administrator whenever the current user lacks read or write permissions. It does not first identify the affected resource, determine whether access is legitimately required, limit the requested permission, or require explicit user authorization before elevation.

Routine JSON parsing and serialization do not normally require administrator privileges. Permission errors should generally be addressed by correcting ownership, selecting a user-writable path, or granting narrowly scoped access. Elevating an entire command or Agent session violates least privilege and expands the security consequences of dependency installation, command execution, malformed inputs, or user mistakes.

Attack Path

  1. A JSON-processing, file-writing, dependency-installation, or validation operation encounters a permission error.
  2. The Agent consults the troubleshooting table.
  3. It follows the recommendation to rerun the operation as administrator.
  4. The original command, package installer, or file-processing operation receives elevated access beyond the task's normal requirements.
  5. Malicious dependencies, unsafe command arguments, or erroneous paths can then affect privileged files and system resources.

Impact Assessment

The guidance can cause commands to obtain administrator-level filesystem and process permissions. On Windows this may provide elevated administrator access; on Unix-like systems, an equivalent e ...[truncated 418 chars]

Remediation
View remediation

Remediation Suggestions

  1. Remove the blanket instruction to run operations as administrator.
  2. Instruct users to identify the exact denied path, operation, and required permission.
  3. Prefer user-writable working directories and correct file ownership or narrowly scoped access-control entries.
  4. Never elevate package installation or commands merely to bypass a permission error.
  5. Require explicit, informed user approval before any operation that genuinely requires elevation.
  6. Elevate only the minimum necessary command rather than the entire Agent session.
  7. Display the exact command, affected resources, justification, and expected changes before requesting approval.
  8. Apply the correction to both duplicate troubleshooting entries at lines 337 and 377.
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 (7)

Vague Triggers

High
Category
Not specified by scanner
Confidence
95% confidence
Finding

The invocation guidance is extremely broad, covering code generation, programming help, debugging, testing, and deployment, which overlaps with common developer requests rather than a narrowly scoped JSON task. In combination with read/exec/write tools, this makes the skill more likely to be auto-selected for many situations where side effects are unnecessary, expanding the attack surface and risk of unintended command or file actions.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
86% confidence
Finding

Marketing the skill as 'ready immediately' or effectively one-click use without concrete invocation constraints encourages indiscriminate activation. For a skill with side-effecting tools, low-friction activation raises the chance that an agent will invoke it before the user understands that files, commands, or external services may be touched.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

The description states '支持中文交互' while the skill branding and content strongly center Chinese-language usage, but there is no explicit opt-in or language selection mechanism. This can violate language/locale policy expectations when a skill appears to force or assume a specific language without user choice.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The skill is branded as a JSON toolkit but advertises unrelated capabilities such as deep vulnerability scanning, CVE correlation, compliance auditing, threat intelligence, and asset risk scoring. This scope expansion can mislead users and agents into invoking the skill for security operations it is not concretely defined to perform, increasing the chance of unsafe tool use, over-privileged execution, or false trust in unsupported security outcomes.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The document extends beyond JSON handling into generic file processing, external API integration, and system command execution, which substantially broadens the skill's authority. When a skill with broad invocation guidance also claims these side-effecting capabilities, an agent may select it for routine tasks and unintentionally perform writes, network access, or shell actions with real system impact.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The skill describes file writes, API integration, and command execution but does not present a clear user-facing warning about persistent system changes, credential use, network egress, or command risks. This omission is dangerous because users may perceive the skill as a harmless JSON helper while it is capable of modifying files and interacting with external systems.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Low
Category
Not specified by scanner
Confidence
89% confidence
Finding

The skill claims commands run in a 'safe sandbox' but provides no actual sandbox definition, isolation guarantees, permission model, or enforcement mechanism. This can create false assurance and cause users or agents to approve command execution under the mistaken belief that harmful filesystem, network, or process effects are contained.

Content

No source excerpt is available for this finding.