apiblaze@0.21.49
APIblaze CLI — Chat with your APIs, Manage your API keys, users and groups with the APIblaze serverless proxy
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe inspected source shows no install-time attack behavior. Credential forwarding follows the caller-provided chat configuration, and the Codex configuration change is reached through an explicit CLI setup flow.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user submits a chat message or invokes the CLI MCP setup flow.
Impact
No unauthorized credential disclosure or unconsented agent configuration change was established.
Mechanism
The widget uses caller-provided configuration and an optional caller-provided token callback; the CLI adds an APIblaze MCP entry after explicit setup selection.
AI rationale
The inspected source shows no install-time attack behavior. Credential forwarding follows the caller-provided chat configuration, and the Codex configuration change is reached through an explicit CLI setup flow.
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a prepublish build and typecheck script, with no install lifecycle hook.
- Codex MCP configuration is written by the CLI install flow, which requires an explicit option or a user selection and performs client authorization.
- The React widget posts messages to its configured endpoint or project URL; an optional bearer token comes from the caller-provided getToken callback, and cookies are omitted unless an endpoint is supplied.
- Suggestion, keyboard, and send-button handlers call the chat function after user interaction in both React builds.
- The browser widget accepts caller-provided endpoint, project, and getToken properties and sends messages on submit.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsMinifiedPossibleObfuscation
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.49.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.21.49 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.