Security audit

Homelab Assets

Security checks for vulnerabilities and agentic risk

Overview

This is a local homelab inventory tracker that openly stores and reports asset details, including sensitive fields like serial numbers and locations.

Install only if you are comfortable keeping homelab inventory details such as serial numbers, purchase prices, service notes, and physical locations in a local plaintext JSON file. Avoid sharing generated JSON, search output, reports, or the bundled example as if it were sanitized production data.

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

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

Natural-Language Policy Violations

Medium

Confidence: 93% confidence
Finding: The example inventory embeds realistic device serial numbers, exact models, physical locations, and operational notes describing the home/lab network layout and services. Even in an example file, this kind of infrastructure detail can aid fingerprinting, social engineering, warranty/support impersonation, or targeted attacks if copied into production use or mistaken for sanitized sample data.

Missing User Warnings

Medium

Confidence: 90% confidence
Finding: The text output prints full serial numbers for any matched asset, which can expose sensitive asset identifiers to anyone able to run the search command or view its output. Serial numbers are often treated as sensitive inventory data because they can aid fraud, warranty abuse, targeted support impersonation, or correlation of physical assets with owners and locations.

Missing User Warnings

Medium

Confidence: 95% confidence
Finding: The JSON mode emits full asset objects without filtering, which can disclose all stored fields including serial numbers, notes, location, and other potentially sensitive inventory metadata. This is riskier than the text path because it enables easy bulk extraction and downstream reuse of sensitive records.

Missing User Warnings

Low

Confidence: 92% confidence
Finding: The skill explicitly stores inventory data in a local JSON file and supports fields such as serial numbers, purchase prices, warranty dates, and physical locations, but the description does not warn users that potentially sensitive asset metadata is persisted on disk. This can lead to unintentional disclosure through local compromise, backups, file sharing, or multi-user systems, especially because physical location and serial data can aid theft, fraud, or insurance abuse.

Missing User Warnings

Low

Confidence: 76% confidence
Finding: This code collects the asset serial number and persists it into the inventory JSON file, which may be sensitive operational data. While the script does print the save path after completion, there is no prior warning, confirmation, or explanatory comment/docstring indicating that sensitive identifiers will be stored.

Static analysis

No suspicious patterns detected.