dbhub-setup

Fail

Audited by Snyk on Aug 13, 2026

Risk Level: CRITICAL
Full Analysis

CRITICAL E005: Suspicious download URL detected in skill instructions.

  • Suspicious download URL detected (high risk: 0.90). The list contains non-official/placeholder registry URLs (registry.example), a truncated/malformed npm tarball URL, and an npm registry URL using a nonstandard port (registry.npmjs.org:444) — all signs of an untrusted or malformed download source that could be used to distribute packages or executables outside the official npm registry policy enforced by the skill.

MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).

  • Third-party content exposure detected (medium risk: 0.30). In the required qualification workflow, the Node qualifier reads free-form text from the DBHub MCP tool via parseToolPayload() by concatenating any returned text fields from result.content and then JSON-parsing it at runtime.

MEDIUM W012: Unverifiable external dependency detected (runtime URL that controls agent).

  • Potentially malicious external URL detected (high risk: 0.90). The qualification manager calls the official npm registry (https://registry.npmjs.org) at runtime (npm pack / npm install) to download the @bytebase/dbhub tarball which is subsequently executed (dist/index.js), so remote code from that URL is fetched and run.

Issues (3)

E005
CRITICAL

Suspicious download URL detected in skill instructions.

W011
MEDIUM

Third-party content exposure detected (indirect prompt injection risk).

W012
MEDIUM

Unverifiable external dependency detected (runtime URL that controls agent).

Audit Metadata
Risk Level
CRITICAL
Analyzed
Aug 13, 2026, 09:49 AM
Issues
3
Security Audit — snyk — dbhub-setup