apiblaze@0.21.6
APIblaze CLI — Chat with your APIs, Manage your API keys, users and groups with the APIblaze serverless proxy
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package contains an explicit capability to alter Codex MCP configuration, which warrants a warning under the policy. Static inspection found no install lifecycle hook or concrete covert attack behavior.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
The user runs the apichat command with --install-mcp codex.
Impact
This adds an agent-accessible MCP endpoint and may include supplied API credentials; no automatic or unconsented activation was found.
Mechanism
The command writes an APIblaze MCP server block to the Codex configuration file.
AI rationale
The package contains an explicit capability to alter Codex MCP configuration, which warrants a warning under the policy. Static inspection found no install lifecycle hook or concrete covert attack behavior.
Evidence
dist/index.js~/.codex/config.toml
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The package exposes a CLI entrypoint and has no npm install lifecycle hook.
- The explicit apichat MCP-install option can add an MCP server to an external agent CLI.
- The Codex installation routine writes a new MCP server block into the user's Codex configuration.
Evidence against
- The agent configuration change requires an explicit CLI option.
- Existing non-APIblaze MCP entries with the same name are rejected rather than replaced.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsPossibleObfuscationUrlStrings
Source & flagged code
8 flaggeddist/index.jsView file
77const raw = fs.readFileSync(CREDENTIALS_PATH, "utf-8");
L78: return JSON.parse(raw);
L79: } catch {
...
L83: function getAccessToken() {
L84: const fromEnv = process.env.APIBLAZE_TOKEN;
L85: if (fromEnv && fromEnv.trim()) return fromEnv.trim();
...
L104: path = __toESM(require("path"));
L105: APIBLAZE_DIR = path.join(os.homedir(), ".apiblaze");
L106: CREDENTIALS_PATH = path.join(APIBLAZE_DIR, "credentials.json");
...
L116: agentCall: () => agentCall,
L117: bothDoorsBody: () => bothDoorsBody,
L118: checkProxyName: () => checkProxyName,
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 {
...
L83: function getAccessToken() {
L84: const fromEnv = process.env.APIBLAZE_TOKEN;
L85: if (fromEnv && fromEnv.trim()) return fromEnv.trim();
...
L104: path = __toESM(require("path"));
L105: APIBLAZE_DIR = path.join(os.homedir(), ".apiblaze");
L106: CREDENTIALS_PATH = path.join(APIBLAZE_DIR, "credentials.json");
...
L116: agentCall: () => agentCall,
L117: bothDoorsBody: () => bothDoorsBody,
L118: checkProxyName: () => checkProxyName,
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
3 Critical6 High3 Medium5 Low
CriticalCredential Exfiltrationdist/index.js
CriticalTrigger Reachable Dangerous Capabilitydist/index.js
CriticalPrevious Version Dangerous Deltadist/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
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.6.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.21.6 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.