Security audit

ColorKit

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-only ColorKit helper skill with a user-run, unpinned install command that users should treat cautiously.

Before installing, prefer a pinned npm package version and a reviewed Git commit or release tag instead of resolving the latest `npx` package or a mutable GitHub branch. Run the install without administrator privileges and review the repository source if supply-chain assurance matters.

A.I.G

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: references/Setup.md:26
Finding: Unpinned npx Package and Mutable Remote Skill Source
Content: View full analysis
Remediation: View remediation
add --skill ColorKit ``` 2. Pin the GitHub source to a specific reviewed commit or immutable release artifact if the installer supports that syntax. 3. Record and verify package integrity hashes or signatures before execution. 4. Prefer installing a reviewed CLI package through a lockfile-based project dependency and invoking its local binary instead of allowing `npx` to download an arbitrary current release. 5. Document the expected npm publisher, repository owner, exact version, commit identifier, and verification procedure. 6. Advise users to run the installer without administrative privileges and in an isolated environment where practical. 7. Avoid recommending mutable branches such as `main` for the ColorKit Swift dependency; use an exact reviewed release or commit instead. ]]>

SkillSpector

Vulnerability Patterns

Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (1)

Rp1

Medium

Category: MCP Rug Pull
Confidence: 95% confidence
Finding: The documentation instructs users to run npx skills add without pinning a specific package version or commit, which can cause execution of whatever package version npx resolves at install time. If the upstream package, dependency chain, or registry resolution is compromised, users could fetch and execute unexpected code during installation of the agent skill.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.