apiblaze@0.19.22
APIblaze CLI — Chat with your APIs, Manage your API keys, users and groups with the APIblaze serverless proxy
AI Security Review
scanned 3mo ago · by lpm-firewall-aiStatic inspection shows a package-aligned API CLI and opt-in sidecar, not credential harvesting or stealth execution. Scanner findings conflate authenticated service requests and explicit setup behavior with exfiltration.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
User runs `apiblaze init` or `apiblaze sidecar setup`; a configured app later imports `apiblaze/sidecar`.
Impact
Can create project sidecar configuration and proxy approved outbound requests with the APIblaze key; this matches the documented, user-invoked feature.
Mechanism
Explicit API proxy sidecar setup and approved-origin fetch routing.
AI rationale
Static inspection shows a package-aligned API CLI and opt-in sidecar, not credential harvesting or stealth execution. Scanner findings conflate authenticated service requests and explicit setup behavior with exfiltration.
Evidence
package.jsondist/index.jsdist/sidecar/index.jsdist/server/index.jsREADME.md.env.local.gitignoreinstrumentation.tsapp/abz-inspector/page.tsxpages/abz-inspector.tsx~/.apiblaze/credentials.json
Network endpoints6
dashboard.apiblaze.comapi.apiblaze.comauth.apiblaze.comsidecar.abz.runapikeys.apiblaze.comiam.apiblaze.com
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
Evidence against
- package.json has no npm install lifecycle hook; prepublishOnly is publish-time build/typecheck.
- dist/index.js only writes project files through explicit `apiblaze init`/`sidecar setup` commands.
- dist/sidecar/index.js routes only explicitly approved HTTPS origins; unapproved calls remain direct.
- Credential tokens are sent to documented APIblaze service hosts for login, control-plane, and sidecar operations.
- child_process use is limited to opening login URLs and the explicit setup command's package install.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
5 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");
...
L123: async function createProxyAnonymous(body) {
L124: const res = await fetch(`${PUBLIC_API_BASE}/proxy`, {
L125: method: "POST",
L126: headers: { "Content-Type": "application/json" },
L127: body: JSON.stringify(body)
L128: });
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");
...
L123: async function createProxyAnonymous(body) {
L124: const res = await fetch(`${PUBLIC_API_BASE}/proxy`, {
L125: method: "POST",
L126: headers: { "Content-Type": "application/json" },
L127: body: JSON.stringify(body)
L128: });
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 Critical3 High3 Medium5 Low
CriticalCredential Exfiltrationdist/index.js
CriticalTrigger Reachable Dangerous Capabilitydist/index.js
HighChild Processdist/index.js
HighSame File Env Network Executiondist/index.js
HighSandbox Evasion Gated Capabilitydist/index.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to apiblaze@0.19.22.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.19.22 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.