Security audit

DebugBundle

Security checks for vulnerabilities and agentic risk

Overview

The plugin is mostly coherent for DebugBundle monitoring, but it exposes broad optional admin, credential, billing, and deletion tools that deserve review before installation.

Install only if you intend your agent to work with DebugBundle using your member or CLI credentials. Keep mutation tools disabled unless needed, and be especially careful before allowing project deletion, billing capacity changes, member changes, token creation/revocation, public status publishing, webhook/Slack/GitHub administration, or alert/probe/health-check changes.

SkillSpector

SkillSpector was not run because this plugin release contains no bundled skills.

Static analysis

Detected: suspicious.dynamic_code_execution, suspicious.env_credential_access, suspicious.exposed_secret_literal (+1 more)

Dynamic code execution detected.

Critical

Code: suspicious.dynamic_code_execution
Location: dist/index.js:30702
Evidence: const makeValidate = new Function(`${names_1.default.self}`, `${names_1.default.scope}`, sourceCode);

Environment variable access combined with network send.

Critical

Code: suspicious.env_credential_access
Location: dist/index.js:6590
Evidence: const llhttpWasmData = process.env.JEST_WORKER_ID ? require_llhttp_wasm() : void 0;

File appears to expose a hardcoded API secret or token.

Critical

Code: suspicious.exposed_secret_literal
Location: dist/index.js:84851
Evidence: var BEARER = [REDACTED])\s+[A-Za-z0-9._~+\/-]{6,}/gi;

Sensitive-looking file read is paired with a network send.

Warn

Code: suspicious.potential_exfiltration
Location: dist/index.js:83364
Evidence: rawAuthState = await readFile(authFilePath);