Skills/npm/dbhub

dbhub@2.0.0

CAUTION· not started

Publisher claims: "Token-efficient database MCP server for PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, ClickHouse, SQLite" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher bytebase · publishing for 618 daysInstalls 240KLast detonated 18 h ago

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
DB_PASSWORDDBHUB_AUTH_TOKENDSNSSH_AUTH_SOCKSSH_PASSWORD or --ssh-password / --auth-tokenConfiguration, not credentials: DB_HOST, DB_NAME, DB_PORT, DB_TYPE, DB_USER, DBHUB_ALLOWED_HOSTS, DBHUB_HOST, MAX_ROWS, READONLY, SQLITE_MEMORY_PATH, SSH_HOST, SSH_KEEPALIVE_COUNT_MAX, SSH_KEEPALIVE_INTERVAL, SSH_KEY, SSH_PASSPHRASE, SSH_PORT, SSH_PROXY_JUMP, SSH_USER, TRANSPORT
Where it talks to
no vendor host named in the codeAlso dbhub.ai, windows.net — not the publisher's domain; check what for before connecting.
What we saw when it ran
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names dbhub.ai, windows.net as well as its own vendor. The guard injects DB_PASSWORD, DBHUB_AUTH_TOKEN, DSN, SSH_AUTH_SOCK, SSH_PASSWORD only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- npx -y @bytebase/dbhub

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

What changed since 1.6.1

vet-skills diff dbhub 1.6.1 2.0.0

In the sandbox, this version reached for nothing 1.6.1 did not. Compared from the two recorded runs, not from source.

1.6.1 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only.

The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-19 and scored it 77/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; References a credential file in the home directory; References a credential file in the home directory. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 15 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
15sprocessdependency install exit 1 · (Use `node --trace-warnings ...` to show where the warning was created) npm error Cannot read properties of null (reading 'edgesOut') npm error A complete log of this run can be found in: /tmp/ks-detonate-AzAexJ/task/home/.npm/_logs/2026-11-19T06_38_05_691Z-debug-0.log
15sclaimednot started: dependency install failed (exit 1); the server itself was not observed
15sprocessscript backend runs setup only
15sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathsdist/chunk-TKSRDSWR.js:83 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"~/.ssh/id_ed25519",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
References a credential file in the home directorydist/chunk-TKSRDSWR.js:82 · References a credential file in the home directory"~/.ssh/id_rsa",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST03
HIGH
References a credential file in the home directorydist/chunk-TKSRDSWR.js:83 · References a credential file in the home directory"~/.ssh/id_ed25519",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST03
HIGH
Access to sensitive file pathsdist/chunk-TKSRDSWR.js:472 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files`Skipping unusable SSH private key from ~/.ssh/config for ${desc} (${unusableReason}).`Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/chunk-TKSRDSWR.js:84 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"~/.ssh/id_ecdsa",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/chunk-TKSRDSWR.js:85 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"~/.ssh/id_dsa"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
References a credential file in the home directorydist/chunk-TKSRDSWR.js:84 · References a credential file in the home directory"~/.ssh/id_ecdsa",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST03
HIGH
Access to sensitive file pathsdist/index.js:1934 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files5. .env file: DSN=your-connection-stringFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
References a credential file in the home directorydist/chunk-TKSRDSWR.js:85 · References a credential file in the home directory"~/.ssh/id_dsa"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST03
HIGH
Access to sensitive file pathsdist/chunk-TKSRDSWR.js:82 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"~/.ssh/id_rsa",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
LOW
Unpinned dependencydist/chunk-L7QAKWJB.js:38 · Unpinned dependency…l. Delete the npx cache directory (${npxCacheDir}) and restart, or upgrade npm (npm install -g npm@latest).`; } return `${cause} Install it next to DBHub (for a global install: npm …Fix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.
AST06
MEDIUM
Process kill commanddist/mysql-OATNYBXM.js:285 · Process kill command — agent can terminate processes* Best-effort server-side kill for a query abandoned by mysql2's client-sideFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
npx invocation of non-well-known packagedist/chunk-L7QAKWJB.js:38 · npx invocation of non-well-known package — may execute untrusted code…criptPath); if (npxCacheDir) { return `${cause} DBHub is running from the npx cache, where some npm versions drop optional driver packages when upgrading a cached i…Fix: Pin versions and sources; vendor anything fetched at install time.
AST06

Cost to the agent

Instructions loaded
≈61 tok
1 file · 38 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for @bytebase/dbhub@2.0.0 as of 18 h ago. This is the package itself, not its dependencies.

What would make this Verified

3 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim bytebase: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
  3. References a credential file in the home directory≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
  4. Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
  5. npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
  6. Unpinned dependencies≈ +1 on the totalPin exact versions (and ideally hashes) in package.json, requirements or the install script so the bundle cannot change under you.
Publish a new version to npm, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim bytebasePropose a patch to the maintainer