apiblaze@0.21.5
APIblaze CLI — Chat with your APIs, Manage your API keys, users and groups with the APIblaze serverless proxy
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo automatic installation behavior or hidden execution was found. The explicit credential-forwarding proxy and agent configuration capabilities remain a real conditional risk.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs an MCP installation command or imports and enables the sidecar with an APIblaze token.
Impact
A service-controlled route can receive application request data and forwarded API-key material; installed MCP servers extend the agent's available remote tools.
Mechanism
Remote MCP configuration and fetch interception with credential forwarding.
AI rationale
No automatic installation behavior or hidden execution was found. The explicit credential-forwarding proxy and agent configuration capabilities remain a real conditional risk.
Evidence
dist/index.jsdist/sidecar/index.js.codex/config.toml
Network endpoints1
sidecar.abz.run
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The package has no npm install lifecycle hook; its only publish hook builds and type-checks.
- An explicit CLI flag installs an MCP server into Codex configuration and can include an API key header.
- The sidecar replaces global fetch and forwards an existing x-api-key to a route supplied by its service.
Evidence against
- The MCP installation is tied to explicit user commands or interactive flows, not package installation.
- The sidecar only activates when imported, enabled, and supplied an APIblaze token; otherwise it returns without changing fetch.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsPossibleObfuscationUrlStrings
Source & flagged code
7 flaggeddist/index.jsView file
77const raw = fs.readFileSync(CREDENTIALS_PATH, "utf-8");
L78: return JSON.parse(raw);
L79: } catch {
...
L102: path = __toESM(require("path"));
L103: APIBLAZE_DIR = path.join(os.homedir(), ".apiblaze");
L104: CREDENTIALS_PATH = path.join(APIBLAZE_DIR, "credentials.json");
...
L114: agentCall: () => agentCall,
L115: bothDoorsBody: () => bothDoorsBody,
L116: checkProxyName: () => checkProxyName,
...
L131: async function createProxyAnonymous(body) {
L132: const res = await fetch(`${PUBLIC_API_BASE}/proxy`, {
L133: method: "POST",
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L7777Trigger-reachable chain: manifest.main -> dist/index.js
L77: const raw = fs.readFileSync(CREDENTIALS_PATH, "utf-8");
L78: return JSON.parse(raw);
L79: } catch {
...
L102: path = __toESM(require("path"));
L103: APIBLAZE_DIR = path.join(os.homedir(), ".apiblaze");
L104: CREDENTIALS_PATH = path.join(APIBLAZE_DIR, "credentials.json");
...
L114: agentCall: () => agentCall,
L115: bothDoorsBody: () => bothDoorsBody,
L116: checkProxyName: () => checkProxyName,
...
L131: async function createProxyAnonymous(body) {
L132: const res = await fetch(`${PUBLIC_API_BASE}/proxy`, {
L133: method: "POST",
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 · L77Findings
2 Critical6 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
HighTrigger Reachable Credential Exfiltrationdist/index.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
Affected versions and remediation
This report applies to apiblaze@0.21.5.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.21.5 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.