Back to skill

Security audit

ia-postgresql

Security checks for vulnerabilities and agentic risk

Overview

This is a PostgreSQL guidance skill with scoped documentation and examples, not an executable or persistent integration.

Installers should treat this as advisory PostgreSQL documentation. Before applying generated SQL to production, review it against your PostgreSQL version, data size, lock budget, migration policy, and language/search-locale needs, and run destructive or write-heavy examples only with explicit authorization and rollback planning.

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
  • 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 (2)

Hidden Instructions

High
Category
Prompt Injection
Confidence
70% confidence
Finding

Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.

Content

Scanner excerpt · SPEC.md (reported line 16)May include surrounding context.

md
Out of scope:
- Acting as the runtime instructions themselves (those live in `SKILL.md`).
- Trigger phrasings already covered by adjacent `ia-*` skills (`validate-plugin` flags >70% description overlap as DUPLICATE_TRIGGER).
- <!-- to fill in: domain-specific exclusions when the skill drifts -->

## Trigger Context

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
91% confidence
Finding

The document repeatedly hard-codes the PostgreSQL text search language as 'english' in indexing, querying, and highlighting examples. Because this is natural-language guidance in a general reference file rather than a region-specific or English-only skill, it establishes an English locale by default without user opt-in or explanation.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.