apiblaze@0.21.9
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 has no install lifecycle hook, but its explicit agent setup changes an external control surface and enables material account actions. This meets the policy threshold for a non-blocking dangerous-capability warning.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
The user invokes a CLI command with --install-mcp and selects or supplies the external agent CLI.
Impact
A configured agent can create proxies, add logins, invite teammates, and point domains in the user's APIblaze account.
Mechanism
The command writes or replaces its own named MCP server block in the Codex configuration and connects the agent to the APIblaze service.
AI rationale
The package has no install lifecycle hook, but its explicit agent setup changes an external control surface and enables material account actions. This meets the policy threshold for a non-blocking dangerous-capability warning.
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
- Package scripts contain no install lifecycle hook.
- The CLI offers external-agent setup through an explicit --install-mcp option and restricts its value to Claude or Codex.
- The Codex setup path rewrites the named MCP entry in the user configuration, but refuses to touch a same-named entry that is not an APIblaze URL.
- The docs command states that the connected agent can act on the user's account, including creating proxies and inviting teammates.
Evidence against
- No automatic installation trigger, hidden payload loading, credential harvesting, or unrelated exfiltration path was identified in the inspected entrypoint.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsPossibleObfuscationUrlStrings
Source & flagged code
7 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
2 Critical6 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
HighTrigger Reachable Credential Exfiltrationdist/index.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
Affected versions and remediation
This report applies to apiblaze@0.21.9.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.21.9 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.