apiblaze@0.17.21
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-aiThe scanner’s credential/network correlation matches the package’s documented CLI and sidecar functionality. All impactful behavior is command-triggered and package-aligned; no malicious chain was established.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
User runs apiblaze login, init, sidecar setup, or another named CLI command.
Impact
Authorized API tokens and approved proxied traffic are sent to APIblaze endpoints as part of the advertised service; no covert harvesting or install-time action was found.
Mechanism
User-invoked API management and approved-origin request proxying.
AI rationale
The scanner’s credential/network correlation matches the package’s documented CLI and sidecar functionality. All impactful behavior is command-triggered and package-aligned; no malicious chain was established.
Evidence
package.jsondist/index.jsdist/sidecar/index.jsdist/server/index.jsREADME.md~/.apiblaze/credentials.json~/.apiblaze/llm.json.env.local.gitignoreinstrumentation.ts
Network endpoints4
dashboard.apiblaze.comapi.apiblaze.comauth.apiblaze.comsidecar.abz.run
Decision evidence
public snapshotAI called this Clean at 97.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
Evidence against
- package.json has only prepublishOnly; no install lifecycle hook.
- dist/index.js performs network and filesystem actions only through named CLI commands.
- Credentials and optional LLM keys are stored locally under ~/.apiblaze with mode 0600.
- dist/sidecar/index.js routes requests only after explicit setup and approved-origin configuration.
- Sidecar reports an unapproved origin only; it otherwise leaves the request direct.
- No hidden payload, eval/vm execution, or unconsented agent-control-surface mutation found.
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.17.21.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.17.21 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.