Back to skill

Security audit

smart-web-components-usage

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-only skill for a UI component library, with no executable code or hidden runtime behavior.

Install this as component-library documentation. Developers should still add confirmation and recovery expectations around delete callbacks, and ensure upload endpoints are appropriate before sending sensitive files.

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
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (6)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

This markdown file documents a destructive delete capability via onRemoteDelete, but the description provides no warning about data loss, irreversibility, or the need for confirmation before deletion. Under the markdown-specific SQP-2 criteria, user-facing documentation should warn when behaviour can affect user data or system integrity.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
85% confidence
Finding

The example shows api.deleteDept(key) and only reports success afterward, but the surrounding documentation does not warn readers that this operation removes data. For markdown files, examples that demonstrate destructive actions should include clear warnings about their impact on user data.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
82% confidence
Finding

This markdown section documents upload and removal capabilities, including large-file upload and deletion confirmation, but does not include any user-facing warning that files may be transmitted to remote services or may affect user data/privacy. Under the markdown-specific missing-warning rule, documentation for behaviors affecting user data should disclose such impact clearly.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
84% confidence
Finding

The examples show request: uploadFile for editor content and image upload, which can transmit user-provided content to a backend, but the surrounding markdown does not warn about privacy or data handling implications. For markdown files, user-impacting networked behavior should be accompanied by a clear warning.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
90% confidence
Finding

This markdown file uses only Chinese for headings, descriptions, examples, and comments, which imposes a specific language on users without any visible opt-in or justification. Under the policy for natural-language violations, forcing a language or locale without user choice can be a violation unless the regional constraint is documented.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
97% confidence
Finding

This markdown file contains user-facing natural language exclusively in Chinese, and there is no indication that the skill is region-specific or that users can opt into this locale. Under the policy, forcing a specific language without user choice can be a natural-language policy violation.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.