apiblaze@0.21.51
APIblaze CLI — Chat with your APIs, Manage your API keys, users and groups with the APIblaze serverless proxy
AI Security Review
scanned 20d ago · by lpm-firewall-aiSource inspection found no install-time attack or unconsented credential transfer. The scanner’s credential and agent-configuration indicators correspond to user-invoked chat and setup behavior.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user sends a chat message or invokes or confirms MCP setup.
Impact
No unintended credential recipient or automatic foreign agent configuration change was established.
Mechanism
The CLI includes an optional user-supplied model key in a chat request to the configured project host; setup writes the selected proxy configuration.
AI rationale
Source inspection found no install-time attack or unconsented credential transfer. The scanner’s credential and agent-configuration indicators correspond to user-invoked chat and setup behavior.
Evidence
package.jsondist/index.jsdist/react/index.mjsdist/react/index.jsdist/browser/widgets.js
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json points to dist/index.js and defines prepublishOnly as build and typecheck; it has no install lifecycle hook.
- The user supplies an LLM key through an explicit command or password prompt; the CLI stores it locally with restrictive file permissions.
- The CLI sends the optional LLM key with a chat request to the project’s configured MCP host.
- The React widgets send messages from user-triggered send handlers and omit browser credentials unless the endpoint is same-origin.
- Codex MCP configuration is written through the setup flow after a user selection, or when the user explicitly invokes the install option.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
Source & flagged code
8 flaggeddist/index.jsView file
32L33: // package.json
L34: var version;
...
L93: function cacheFile() {
L94: return import_path.default.join(import_os.default.homedir(), ".apiblaze", "cli-policy.json");
L95: }
...
L104: for (const name of CONTROL_PLANE_ENV) {
L105: const v = process.env[name];
L106: try {
...
L154: const base2 = globalThis.fetch.bind(globalThis);
L155: globalThis.fetch = (async (input, init) => {
L156: 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;
...
L93: function cacheFile() {
L94: return import_path.default.join(import_os.default.homedir(), ".apiblaze", "cli-policy.json");
L95: }
...
L104: for (const name of CONTROL_PLANE_ENV) {
L105: const v = process.env[name];
L106: try {
...
L154: const base2 = globalThis.fetch.bind(globalThis);
L155: globalThis.fetch = (async (input, init) => {
L156: 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.51.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.21.51 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.