apiblaze@0.21.38
APIblaze CLI — Chat with your APIs, Manage your API keys, users and groups with the APIblaze serverless proxy
AI Security Review
scanned 27d ago · by lpm-firewall-aiSource inspection supports a clean verdict: agent configuration is performed through an explicit CLI flow, and inspected credential handling relates to the selected API. Scanner hints did not establish credential theft, install-time mutation, or another concrete attack.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Running the CLI agent setup flow that connects an API to an agent.
Impact
Configuration enables the chosen API connection; no malicious effect was established.
Mechanism
The flow adds a named MCP server URL and optional key headers to Codex configuration; target credentials are caller-selected or prompted for.
AI rationale
Source inspection supports a clean verdict: agent configuration is performed through an explicit CLI flow, and inspected credential handling relates to the selected API. Scanner hints did not establish credential theft, install-time mutation, or another concrete attack.
Evidence
dist/index.js
Decision evidence
public snapshotAI called this Clean at 89.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a CLI and library entrypoint; its only lifecycle hook is prepublishOnly, which builds and typechecks.
- The Codex configuration helper writes a named MCP server URL and optional API key headers; the inspected caller performs this during an explicit CLI flow.
- Target credentials are read from a caller-selected environment variable or prompted for interactively, consistent with configuring authentication for the chosen API.
Evidence against
- No inspected source showed credential forwarding to an unrelated or package-controlled recipient.
- No npm install hook or automatic agent configuration mutation was found.
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 {
...
L143: const base2 = globalThis.fetch.bind(globalThis);
L144: globalThis.fetch = (async (input, init) => {
L145: 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 {
...
L143: const base2 = globalThis.fetch.bind(globalThis);
L144: globalThis.fetch = (async (input, init) => {
L145: 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.38.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.21.38 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.