Security audit

Plant Tracker

Security checks for vulnerabilities and agentic risk

Overview

The plant tracker is mostly coherent, but its export command can overwrite broad areas of the user's home directory, which is more authority than a plant-data export needs.

Review the export behavior before installing. Use exports only to clearly intended Markdown files, preferably inside ~/.openclaw/workspace or a dedicated exports folder, and avoid letting the skill write to existing home-directory configuration files or application data.

A.I.G

Vulnerability Patterns

Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
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)

T09 · Insecure Skill Coding Practices

Error

Location: scripts/plant_tracker.py:218
Finding: Unsafe Export Path Validation Allows Arbitrary Home-File Overwrite
Content: View full analysis
Remediation: View remediation

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

Static analysis

No suspicious patterns detected.