apiblaze@0.21.2
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-aiThe scanner findings correspond to an API proxy CLI with explicit setup commands, not an automatic package-install payload. There is no install hook, self-dependency, hidden execution, or confirmed unconsented credential exfiltration.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user explicitly runs sidecar or MCP setup commands.
Impact
Approved requests may be routed through the service, and chosen MCP setup can alter local agent configuration.
Mechanism
User-invoked API proxying and MCP configuration.
AI rationale
The scanner findings correspond to an API proxy CLI with explicit setup commands, not an automatic package-install payload. There is no install hook, self-dependency, hidden execution, or confirmed unconsented credential exfiltration.
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest has no install-time lifecycle hook; its only lifecycle-like hook builds and type-checks before publishing.
- The server library sends only its caller-supplied control-plane key to APIblaze service endpoints.
- The sidecar routes requests only after a user explicitly enables it and an origin has been approved.
- An unapproved origin is left untouched and only reported as a candidate.
Evidence against
- The explicit sidecar setup can modify a project and proxy approved outbound requests, including an existing x-api-key header.
- Explicit MCP commands can write Codex configuration and project agent instructions.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket
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 Critical5 High3 Medium5 Low
CriticalCredential Exfiltrationdist/index.js
CriticalTrigger Reachable Dangerous Capabilitydist/index.js
HighChild Processdist/index.js
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
LowHigh Entropy Strings
Affected versions and remediation
This report applies to apiblaze@0.21.2.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.21.2 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.