apiblaze@0.21.33
APIblaze CLI — Chat with your APIs, Manage your API keys, users and groups with the APIblaze serverless proxy
AI Security Review
scanned 1mo ago · by lpm-firewall-aiSource supports a warning for explicit user-command agent configuration and persistent instructions, including later automatic refreshes. The absence of install hooks and the inspected consent gates do not support the scanner's malicious verdict.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
User selects an agent connection or supplies --install-mcp; later CLI use can refresh previously accepted connections.
Impact
Future agent sessions can call the connected API and follow the added instructions without repeating setup consent.
Mechanism
Writes MCP server configuration and project agent instructions, then remembers the installed choice for later configuration updates.
AI rationale
Source supports a warning for explicit user-command agent configuration and persistent instructions, including later automatic refreshes. The absence of install hooks and the inspected consent gates do not support the scanner's malicious verdict.
Evidence
dist/index.jsconfig.tomlAGENTS.mdCLAUDE.md
Decision evidence
public snapshotAI called this Suspicious at 94.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- package.json has no preinstall, install, or postinstall hook and no runtime self-dependency.
- Agent setup accepts an explicit install flag or an interactive choice.
- The CLI writes MCP configuration to the user's Codex config.toml.
- Agent setup also writes persistent project instructions to AGENTS.md or CLAUDE.md.
- A saved installed preference enables automatic MCP configuration refreshes during later CLI use.
Evidence against
- No concrete malicious install behavior or covert credential harvesting was established.
- Inspected credential handling uses caller-supplied keys for APIblaze services and explicitly configured chat functionality.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
Source & flagged code
8 flaggeddist/index.jsView file
32L33: // package.json
L34: var version;
...
L70: function cacheFile() {
L71: return import_path.default.join(import_os.default.homedir(), ".apiblaze", "cli-policy.json");
L72: }
...
L81: for (const name of CONTROL_PLANE_ENV) {
L82: const v = process.env[name];
L83: try {
...
L120: const base2 = globalThis.fetch.bind(globalThis);
L121: globalThis.fetch = (async (input, init) => {
L122: const url = typeof input === "string" ? input : input instanceof URL ? input.href : input.url;
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L3232Trigger-reachable chain: manifest.main -> dist/index.js
L32:
L33: // package.json
L34: var version;
...
L70: function cacheFile() {
L71: return import_path.default.join(import_os.default.homedir(), ".apiblaze", "cli-policy.json");
L72: }
...
L81: for (const name of CONTROL_PLANE_ENV) {
L82: const v = process.env[name];
L83: try {
...
L120: const base2 = globalThis.fetch.bind(globalThis);
L121: globalThis.fetch = (async (input, init) => {
L122: const url = typeof input === "string" ? input : input instanceof URL ? input.href : input.url;
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/index.jsView on unpkg · L32Findings
2 Critical7 High3 Medium5 Low
CriticalCredential Exfiltrationdist/index.js
CriticalTrigger Reachable Dangerous Capabilitydist/index.js
HighChild Processdist/index.js
HighShell
HighSame File Env Network Executiondist/index.js
HighCredential Redirect Persistencedist/index.js
HighSandbox Evasion Gated Capabilitydist/index.js
HighCross File Remote Execution Contextdist/index.js
HighTrigger Reachable Credential Exfiltrationdist/index.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
Affected versions and remediation
This report applies to apiblaze@0.21.33.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.21.33 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.