database-schema-designer

Security checks across malware telemetry and agentic risk

Overview

This is a documentation-only database design helper; its examples should be reviewed before use, especially the sample seed password.

Installation is reasonable for a schema-design helper. Review any generated migrations, RLS policies, indexes, and seed data before applying them to a real database, test changes in staging, keep backups, and do not reuse the example admin password outside disposable local development.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • 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 (1)

Missing User Warnings

Medium
Confidence
93% confidence
Finding
The seed-data example hardcodes a concrete password value (`password123`) and does so in a realistic user-creation flow without any warning that it is for local development only. This is dangerous because users frequently copy seed scripts into staging or production-like environments, which can leave predictable credentials in deployed systems or normalize insecure password practices.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal