Security audit

branding

Security checks for vulnerabilities and agentic risk

Overview

This skill provides Pruna brand logos and color guidance, with only a supply-chain caution around unpinned install commands.

Before running the documented npx commands, verify the skills installer version and the PrunaAI/pruna-skills revision you intend to install. Once installed, the skill itself is mainly a local brand kit; use the bundled SVG assets as directed and avoid redrawing or recoloring the logo.

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: SKILL.md:18
Finding: Unpinned Third-Party Packages and Repository References Executed Through npx
Content: View full analysis
Remediation: View remediation
add PrunaAI/pruna-skills@branding ``` 2. Pin repository content to an immutable commit hash or signed release artifact rather than a mutable branch, tag, or skill selector. 3. Commit and verify lockfiles where package-manager workflows support them. Use npm integrity metadata, checksums, or cryptographic signatures to validate downloaded artifacts. 4. Remove `-y` from documentation where practical so users can review the resolved package and installation operation before execution. 5. Prefer a trusted, preinstalled version of the installation tool in controlled environments rather than allowing `npx` to download an executable package on demand. 6. Run installation in a restricted environment with least privilege, limited filesystem access, no unnecessary credentials in environment variables, and constrained outbound network access. 7. Add documentation stating that the installation commands execute third-party code and should only be used after verifying the resolved package version and repository revision. ]]>

SkillSpector

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 (3)

Rp1

Medium

Category: MCP Rug Pull
Confidence: 70% confidence
Finding: npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
Content: No source excerpt is available for this finding.

Rp1

Medium

Category: MCP Rug Pull
Confidence: 70% confidence
Finding: npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
Content: No source excerpt is available for this finding.

Rp1

Medium

Category: MCP Rug Pull
Confidence: 70% confidence
Finding: npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.