apiblaze@0.21.65
APIblaze CLI — Chat with your APIs, Manage your API keys, users and groups with the APIblaze serverless proxy
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe flagged key flow is an explicitly configured, optional BYO-provider-key chat feature, and the key is sent with chat requests to the project's runtime service. The manifest has no install hook; its prepublishOnly script builds and typechecks.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user configures a provider key and starts a chat turn.
Impact
The key is used by the chat service as documented; no unrelated credential transfer was found.
Mechanism
The CLI stores the key locally and includes it in the request to the configured project's runtime-chat endpoint.
AI rationale
The flagged key flow is an explicitly configured, optional BYO-provider-key chat feature, and the key is sent with chat requests to the project's runtime service. The manifest has no install hook; its prepublishOnly script builds and typechecks.
Evidence
package.jsondist/index.js
Network endpoints2
${p.mcpHost}/${p.version}/${p.environment}/runtime-chatapi.apiblaze.com
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The only lifecycle script shown is prepublishOnly, which runs the build and typecheck.
- Users explicitly configure an optional provider key for chat; the CLI stores it locally with mode 0600.
- When a chat turn runs, the configured key is sent to that project's runtime-chat endpoint, matching the documented BYO-key chat feature.
Evidence against
- No unrelated credential collector or concealed execution behavior was identified in the reviewed paths.
- The flagged child-process use is in a user-invoked project setup path; no harmful automatic execution was confirmed.
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.65.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.21.65 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.