Back to skill

Security audit

Sandbox

Security checks for vulnerabilities and agentic risk

Overview

This is a simple local reference skill that prints static sandbox/sysops guidance, with no evidence of credential access, network activity, persistence, or destructive behavior.

Installation appears low risk from a security perspective. Treat it as a static reference helper; be aware that one cheatsheet command name is inaccurate, and direct invocation may depend on execution permissions in the installed environment.

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
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · scripts/script.sh (reported line 64)May include surrounding context.

sh
## Prerequisites
- Basic understanding of sysops concepts
- Required tools and access credentials
- System meeting minimum requirements

## Installation

Intent-Code Divergence

Low
Category
Not specified by scanner
Confidence
98% confidence
Finding

The inline reference table in the cheatsheet claims users can invoke a 'troubleshooting' command, but the dispatcher only implements 'debugging' and no 'troubleshooting' case exists. This is an active documentation-to-code mismatch that can mislead users about the skill's interface.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.