ClawHub
Back to skill

Security audit

rez-resolve-troubleshooting

Security checks for vulnerabilities and agentic risk

Overview

This is a Rez troubleshooting guide whose file-writing and command examples are disclosed, local, and aligned with diagnosing resolve failures.

Install this if you want a step-by-step Rez resolve troubleshooting workflow. Be aware that following it may create local .rxt diagnostic files and display package paths or configuration, so avoid sharing that output publicly if it contains internal repository names or paths.

A.I.G

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

SkillSpector

Vulnerability Patterns
  • Rogue AgentSelf-Modification, Session Persistence
  • 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
Findings (1)

Session Persistence

Medium
Category
Rogue Agent
Confidence
60% confidence
Finding

Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.

Content

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

Step 0 — capture the failure

Never start by debugging inside a subshell; rez-env drops you into an interactive shell on success and hides the structured output on failure. Write the context to a file instead:

bash
rez-env <reqs> -o context.rxt          # also stores a FAILED resolve

Static analysis

No suspicious patterns detected.