apiblaze@0.21.1
APIblaze CLI — Chat with your APIs, Manage your API keys, users and groups with the APIblaze serverless proxy
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo automatic lifecycle attack or covert installation behavior was found. The package still warrants a warning because explicit commands can transmit credentials and persist remote agent-tool access.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Run apiblaze llm set-key followed by chat, or explicitly select/use apichat --install-mcp.
Impact
The APIblaze service receives the configured LLM key during chat, and future agent sessions may access the configured remote API tools.
Mechanism
Forwards a configured LLM key and installs a remote MCP configuration with persistent project instructions.
AI rationale
No automatic lifecycle attack or covert installation behavior was found. The package still warrants a warning because explicit commands can transmit credentials and persist remote agent-tool access.
Evidence
dist/index.js.apiblaze/llm.json.codex/config.tomlAGENTS.mdCLAUDE.md
Decision evidence
public snapshotAI called this Suspicious at 86.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The explicit LLM-key command stores a provider key and chat requests include that key in a network request.
- The explicit MCP-install flow writes a remote MCP entry, including an API-key header when supplied, into the user's Codex configuration.
- After installing an MCP, the CLI writes a persistent instruction block into the current project's agent instruction file.
Evidence against
- package.json has no preinstall, install, or postinstall hook; prepublishOnly is publish-time only.
- The MCP mutation is reachable through an explicit --install-mcp option or an interactive choice, not package installation.
- The key prompt and local storage behavior are exposed by a named llm set-key command.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket
HighEntropyStringsPossibleObfuscationUrlStrings
Source & flagged code
7 flaggeddist/index.jsView file
77const raw = fs.readFileSync(CREDENTIALS_PATH, "utf-8");
L78: return JSON.parse(raw);
L79: } catch {
...
L102: path = __toESM(require("path"));
L103: APIBLAZE_DIR = path.join(os.homedir(), ".apiblaze");
L104: CREDENTIALS_PATH = path.join(APIBLAZE_DIR, "credentials.json");
...
L114: agentCall: () => agentCall,
L115: bothDoorsBody: () => bothDoorsBody,
L116: checkProxyName: () => checkProxyName,
...
L131: async function createProxyAnonymous(body) {
L132: const res = await fetch(`${PUBLIC_API_BASE}/proxy`, {
L133: method: "POST",
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 {
...
L102: path = __toESM(require("path"));
L103: APIBLAZE_DIR = path.join(os.homedir(), ".apiblaze");
L104: CREDENTIALS_PATH = path.join(APIBLAZE_DIR, "credentials.json");
...
L114: agentCall: () => agentCall,
L115: bothDoorsBody: () => bothDoorsBody,
L116: checkProxyName: () => checkProxyName,
...
L131: async function createProxyAnonymous(body) {
L132: const res = await fetch(`${PUBLIC_API_BASE}/proxy`, {
L133: method: "POST",
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 Critical5 High3 Medium5 Low
CriticalCredential Exfiltrationdist/index.js
CriticalTrigger Reachable Dangerous Capabilitydist/index.js
HighChild Processdist/index.js
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
LowHigh Entropy Strings
Affected versions and remediation
This report applies to apiblaze@0.21.1.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.21.1 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.