apiblaze@0.21.46
APIblaze CLI — Chat with your APIs, Manage your API keys, users and groups with the APIblaze serverless proxy
AI Security Review
scanned 22d ago · by lpm-firewall-aiInspected source shows no install-time execution or concrete attack behavior. The flagged Codex configuration change is part of interactive setup, and chat credentials are sent through the caller-configured chat flow.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user chooses to connect an agent in the CLI or sends a chat message.
Impact
No confirmed credential theft, unrelated disclosure, or unconsented agent configuration change.
Mechanism
The CLI writes the selected MCP server entry to Codex configuration. ChatWidget sends its callback token to the supplied endpoint or project runtime URL when the user submits a message.
AI rationale
Inspected source shows no install-time execution or concrete attack behavior. The flagged Codex configuration change is part of interactive setup, and chat credentials are sent through the caller-configured chat flow.
Evidence
~/.codex/config.toml
Network endpoints1
${project}.mcp.${host} runtime-chat
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines only a prepublishOnly build and typecheck hook; it has no install lifecycle hook.
- The Codex MCP entry is added through an interactive agent-connection choice, and the writer saves the selected server configuration while refusing conflicting non-APIblaze entries.
- ChatWidget sends a token returned by the caller's getToken callback to the supplied endpoint or project runtime URL; project mode omits cookies, and endpoint mode uses same-origin cookies.
- Both React bundles and the browser widget trigger chat requests from user send actions.
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.46.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.21.46 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.