Autotable Usage

Security checks across malware telemetry and agentic risk

Overview

This appears to be database schema automation guidance, but it documents high-impact table drop and automatic schema-change behavior without enough safety scoping for production use.

Review the database lifecycle settings before installing or using this skill. Do not enable create, auto-drop, or automatic update behavior against production databases unless you have backups, migration review, explicit approval, and a tested rollback plan. Prefer validate, dry-run, or reviewed migration flows for live systems.

SkillSpector

By NVIDIA

Vulnerability Patterns

Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
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

Findings (3)

Missing User Warnings

Medium

Confidence: 93% confidence
Finding: The document explicitly describes destructive operations such as dropping tables in create mode and auto-dropping unregistered tables, but it does not prominently warn about irreversible data loss or recommend limiting these features to development environments. In a usage/architecture guide, this omission can lead operators or downstream agents to enable dangerous behavior in production and unintentionally destroy schema objects or data.

Missing User Warnings

Medium

Confidence: 91% confidence
Finding: The documentation explicitly describes destructive behaviors such as `create → DROP + CREATE` and deletion of unregistered tables, but it does not pair them with a clear warning about irreversible data loss or safe-use constraints. In a developer-facing automation skill, this is dangerous because users may enable these lifecycle modes in production or misunderstand callbacks/interceptors as sufficient safeguards, leading to accidental schema destruction.

Missing User Warnings

Medium

Confidence: 88% confidence
Finding: The document explicitly promotes automatic schema creation and incremental updates on application restart, but it does not warn that these operations can alter production databases, trigger unintended DDL, or cause outages/data loss if entity changes are incorrect. In a quick-start guide, readers may copy the configuration directly into real environments, making unsafe defaults and missing cautions materially risky.

VirusTotal

57/57 vendors flagged this skill as clean.

View on VirusTotal