Is @tobilu/qmd safe?
- Node.js shell/command execution
- Node.js network egress
- npm prepare hook
What to do: Nothing here argues against installing it. Grant the capabilities it lists only if you expect the tool to need them.
@tobilu/qmd is an npm package analyzed by SkillTotal's deterministic static scanner. The scan found no malicious indicators. It can: install time execution, mcp tools detected, network egress and shell execution — capabilities are what the code can do, not a verdict on intent. Risk score 0/100 (low).
@tobilu/qmd 2.8.3
Automated static-analysis result. It can contain false positives and false negatives, and is not a claim about the intent of @tobilu/qmd's authors. Report a false positive.
Behavioral traits
How this component maps to the CSA agentic threat model. Descriptive — it never affects the risk score.
Findings (4)
The component can run operating-system commands or spawn processes.
import { execFileSync } from "node:child_process";import { spawn as nodeSpawn } from "child_process";import { execFileSync } from "node:child_process";import { spawnSync } from "node:child_process";const result = spawnSync(command, args, {const result = spawnSync("git", args, { cwd: root, encoding: "utf8", stdio: ["pipe", "pipe", "pipe"] });import { spawnSync } from "node:child_process";const result = spawnSync(command, args, {Why it matters: Powerful and often legitimate — confirm the commands aren't built from untrusted input.
Fix: Confirm the command and its arguments are fully controlled and not derived from untrusted input; prefer execFile with an argument array.
package.json has a 'prepare' script (runs on git/local installs and before publishing).
"prepare": "node scripts/install-hooks.mjs && node scripts/build.mjs",
Why it matters: Usually a build step, but confirm it doesn't fetch or run remote code.
Fix: Usually a legitimate build step; confirm it only builds and does not fetch or execute remote code.
The component makes outbound network requests.
const resp = await fetch(url, { method: "HEAD" });import { createServer } from "node:http";const response = await mcpHandler.fetch(request, parsedBody !== undefined ? { parsedBody } : undefined);Why it matters: Usually legitimate, but confirm the destinations are expected and no sensitive data leaves.
Fix: Confirm the destination hosts are expected and that no sensitive data is sent off-host.
An MCP tool surface (manifest or tool definitions) was found.
const server = new McpServer({ name: "qmd", version: getPackageVersion() }, {server.registerTool("query", {server.registerTool("get", {server.registerTool("multi_get", {server.registerTool("status", {Why it matters: Just context — review which tools it offers and their permissions.
Fix: Review the declared MCP tools and their permissions.
How attackers abuse these capabilities
Interactive labs on the attack class behind the rules above. They show the technique, not anything found in @tobilu/qmd.
Check your own component
Run the same evidence-backed scan on any MCP server, agent skill, or package.
Scan your own componentHow we determine this: deterministic static analysis (regex + AST), evidence-anchored, no code execution. Methodology →