apiblaze@0.21.48
APIblaze CLI — Chat with your APIs, Manage your API keys, users and groups with the APIblaze serverless proxy
AI Security Review
scanned 21d ago · by lpm-firewall-aiThe source shows an explicitly offered MCP setup that persists and can refresh the Codex configuration on later apichat runs. This is a guarded agent-configuration capability, with no confirmed malicious behavior or install-time trigger.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Running apichat and choosing to add the proxy MCP to a detected agent; later runs reuse the saved installed choice.
Impact
The connected agent gains access to the configured API tools, and its MCP configuration can be updated on later CLI runs.
Mechanism
The CLI writes a named MCP server entry to the Codex configuration and refreshes it after checking the endpoint.
AI rationale
The source shows an explicitly offered MCP setup that persists and can refresh the Codex configuration on later apichat runs. This is a guarded agent-configuration capability, with no confirmed malicious behavior or install-time trigger.
Evidence
dist/index.js~/.codex/config.toml
Decision evidence
public snapshotAI called this Suspicious at 86.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest’s prepublishOnly script runs build and typecheck; it shows no install-time hook.
- During apichat setup, the CLI asks whether to add this proxy’s MCP to an agent or chat directly, and records a successful installation.
- The Codex integration builds a named MCP server entry using the proxy URL and writes it to the Codex config file.
- On later apichat runs, a previously installed integration is refreshed after the endpoint check succeeds.
- The integration setup is reached from the apichat command path.
Evidence against
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.48.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.21.48 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.