postgresql-database-engineering

Fail

Audited by Snyk on Aug 5, 2026

Risk Level: CRITICAL
Full Analysis

HIGH W007: Insecure credential handling detected in skill instructions.

  • Insecure credential handling detected (high risk: 1.00). The skill includes examples that embed plaintext passwords and connection strings (e.g., CREATE USER ... PASSWORD 'secure_password', primary_conninfo with password, CONNECTION '... password=pass', FOREIGN DATA WRAPPER user mapping with password), which requires the LLM to produce secret values verbatim in commands/configs — an insecure pattern that risks credential exposure.

CRITICAL E006: Malicious code pattern detected in skill scripts.

  • Malicious code pattern detected (high risk: 1.00). The content includes an explicit credential-exfiltration pattern: a SECURITY DEFINER auth function that reads pg_shadow and is granted to PUBLIC, combined with a pgbouncer auth_query—this directly exposes password hashes and enables credential theft / unauthorized access.

MEDIUM W013: Attempt to modify system services in skill instructions.

  • Attempt to modify system services in skill instructions detected (high risk: 1.00). The skill includes explicit system-level commands that stop/start services, remove and modify files under /var/lib/postgresql, and edit system configuration (postgresql.conf, pg_hba.conf), which require elevated privileges and directly change the host machine's state.

Issues (3)

W007
HIGH

Insecure credential handling detected in skill instructions.

E006
CRITICAL

Malicious code pattern detected in skill scripts.

W013
MEDIUM

Attempt to modify system services in skill instructions.

Audit Metadata
Risk Level
CRITICAL
Analyzed
Aug 5, 2026, 02:50 PM
Issues
3
Security Audit — snyk — postgresql-database-engineering