apiblaze@0.21.18
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 is not malicious by static evidence, but it has a concrete explicit-command capability to configure an external AI agent. This fits a non-blocking agent capability warning rather than an install-hook attack.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
The user runs the CLI with the MCP installation option or selects an external agent in its prompt.
Impact
This grants the chosen agent access to the configured API proxy; no unconsented installation or confirmed exfiltration was found.
Mechanism
The CLI reads and updates the Codex configuration to add its MCP server.
AI rationale
The package is not malicious by static evidence, but it has a concrete explicit-command capability to configure an external AI agent. This fits a non-blocking agent capability warning rather than an install-hook attack.
Evidence
dist/index.js
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The manifest has no npm install lifecycle hook; its listed lifecycle-like script is prepublish-only.
- The CLI only proceeds noninteractively when the caller supplies the install option.
- In interactive use, it presents a choice before connecting an external agent.
- The Codex installation routine reads and rewrites the user's Codex configuration.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsPossibleObfuscationUrlStrings
Source & flagged code
8 flaggeddist/index.jsView file
77const raw = fs2.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: path2 = __toESM(require("path"));
L105: APIBLAZE_DIR = path2.join(os2.homedir(), ".apiblaze");
L106: CREDENTIALS_PATH = path2.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 = fs2.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: path2 = __toESM(require("path"));
L105: APIBLAZE_DIR = path2.join(os2.homedir(), ".apiblaze");
L106: CREDENTIALS_PATH = path2.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.18.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.21.18 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.