Back to skill

Security audit

SFSymbolsKit

Security checks for vulnerabilities and agentic risk

Overview

The skill appears to do what it says: validate Apple SF Symbol names, with a disclosed third-party Swift package addition users should review before applying.

Install is reasonable if you want grounded SF Symbol lookup. Before letting an agent modify a project, confirm you want the SFSymbolsKit dependency, review the repository, and prefer pinning to a reviewed exact version or commit for production or CI use.

Vulnerability Patterns
  • 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
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)

T08 · Insecure Dependencies

Warning
Location
SKILL.md:49
Finding

Unpinned Third-Party Swift Package Creates a Supply-Chain Execution Risk

Content
View full analysis
Remediation
View remediation
" ) ``` 4. Alternatively, use an exact, reviewed release rather than a compatible version range, and commit `Package.resolved` to preserve the reviewed resolution. 5. Verify release provenance, repository ownership, commit signatures, and checksums where available. 6. Restrict dependency resolution and builds in CI using sandboxing, minimal filesystem permissions, network controls, and narrowly scoped secrets. 7. Establish an update-review process so dependency revisions are scanned and approved before adoption. ]]>
Vulnerability Patterns
  • 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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

Ae1

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 58)May include surrounding context.

md
in the catalog — always trust `symbols.json`'s `property`, never a