@milpa/comal@0.2.0
Comal: governed operations, execution receipts, and programming assistance in any language
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe default route sends OPENAI_API_KEY to a package-selected local-network hostname rather than an endpoint the user chose for OpenAI. This is a concrete credential disclosure path; the Unicode finding itself is a sanitizer and does not affect the verdict.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs the CLI without choosing an endpoint while OPENAI_API_KEY is set, then makes a model request.
Impact
A service reached through that local hostname can capture and misuse the user's OpenAI credential.
Mechanism
The provider defaults to http://llama.local:11438/, loads OPENAI_API_KEY, and sends it in the Authorization Bearer header.
Attack narrative
When a CLI run has no explicitly selected endpoint, the OpenAI-compatible provider falls back to http://llama.local:11438/. If OPENAI_API_KEY is present, it reads that value and sends it as a Bearer token with provider requests. The executable reaches this connection path during normal CLI use. The README identifies llama.local as an endpoint from the original environment and instructs users to select a connection, but the runtime still uses it as the default.
AI rationale
The default route sends OPENAI_API_KEY to a package-selected local-network hostname rather than an endpoint the user chose for OpenAI. This is a concrete credential disclosure path; the Unicode finding itself is a sanitizer and does not affect the verdict.
Evidence
src/openai-provider.mjssrc/cli.mjsbin/comal.mjsREADME.md
Network endpoints1
llama.local:11438/
Decision evidence
public snapshotAI called this Malicious at 91.0% confidence as Malware with low false-positive risk.
Evidence for block
- The OpenAI-compatible provider defaults to http://llama.local:11438/ when no endpoint is configured.
- The default OpenAI provider reads OPENAI_API_KEY and adds it as a Bearer authorization header to requests.
- A non-demo CLI run connects with the selected settings, and the package executable invokes that CLI.
- The README describes llama.local as belonging to the original environment and tells users to select their connection explicitly.
Evidence against
- The package has no lifecycle scripts, so this credential flow is not triggered during installation.
- The separate auth-provider flow checks that credentials go only to that provider's configured origin.
- The flagged Unicode characters are stripped by a sanitizer in the relay output-boundary helper.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkWebSocket
Source & flagged code
7 flaggednode_modules/ajv/dist/compile/jtd/serialize.jsView file
49sourceCode = `${gen.scopeRefs(names_1.default.scope)}return ${serializeFuncCode}`;
L50: const makeSerialize = new Function(`${names_1.default.scope}`, sourceCode);
L51: const serialize = makeSerialize(this.scope.get());
Low
Eval
Package source references a known benign dynamic code generation pattern.
node_modules/ajv/dist/compile/jtd/serialize.jsView on unpkg · L49node_modules/ajv/dist/vocabularies/dynamic/recursiveAnchor.jsView file
2Object.defineProperty(exports, "__esModule", { value: true });
L3: const dynamicAnchor_1 = require("./dynamicAnchor");
L4: const util_1 = require("../../compile/util");
Medium
Dynamic Require
Package source references dynamic require/import behavior.
node_modules/ajv/dist/vocabularies/dynamic/recursiveAnchor.jsView on unpkg · L2Findings
2 Critical1 High6 Medium5 Low
CriticalTrojan Source Unicodesrc/plugins/open-relay/bound.mjs
CriticalTrigger Reachable Dangerous Capabilitysrc/plugin-notices.mjs
HighSemantic Analysis Limitednode_modules/ajv/dist/runtime/parseJson.js#virtual:normalized:round1
MediumDynamic Requirenode_modules/ajv/dist/vocabularies/dynamic/recursiveAnchor.js
MediumNetwork
MediumEnvironment Vars
MediumShips Wasm Modulenode_modules/@jitl/quickjs-wasmfile-debug-asyncify/dist/emscripten-module.wasm
MediumShips Build Helpersrc/windows-private.ps1
MediumStructural Risk Force Deep Review
LowEvalnode_modules/ajv/dist/compile/jtd/serialize.js
LowFilesystem
Low
Affected versions and remediation
This report applies to @milpa/comal@0.2.0.
See all versions of @milpa/comal for other recorded verdicts.
- Avoid installing @milpa/comal@0.2.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.