fraim@2.0.294
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe CLI setup enables global Claude Code metrics without a separate telemetry opt-in, and the runtime can forward captured usage metrics to FRAIM analytics. This is a real configuration and privacy risk, but the source supports a warning rather than a malware block.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
Running `fraim init-project` when Claude Code is detected, or configuring Claude Code with `fraim add-ide`.
Impact
Claude Code usage metrics may leave the host for FRAIM analytics. The inspected path did not show prompt text or service credentials in that transfer.
Mechanism
The CLI writes telemetry settings to `~/.claude/settings.json`; the local receiver captures token metrics, and a `seekMentoring` event can include a captured snapshot before usage events are uploaded.
AI rationale
The CLI setup enables global Claude Code metrics without a separate telemetry opt-in, and the runtime can forward captured usage metrics to FRAIM analytics. This is a real configuration and privacy risk, but the source supports a warning rather than a malware block.
Evidence
dist/src/cli/commands/init-project.jsdist/src/cli/commands/add-ide.jsdist/src/cli/setup/claude-code-telemetry.jsdist/src/local-mcp-server/otlp-metrics-receiver.jsdist/src/local-mcp-server/stdio-server.jsdist/src/local-mcp-server/usage-collector.js~/.claude/settings.json
Network endpoints2
localhost:4318fraim.wellnessatwork.me
Decision evidence
public snapshotAI called this Suspicious at 89.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- `init-project` enables Claude Code telemetry at user scope when Claude Code is detected; `add-ide` also enables it when configuring Claude Code.
- The setup enables Claude Code telemetry and points metric export to a local receiver, then writes the settings to `~/.claude/settings.json`.
- The receiver parses Claude token usage metrics; a `seekMentoring` call can capture a token snapshot and attach it to a usage event.
- The MCP server uploads usage events to its configured remote URL, defaulting to `https://fraim.wellnessatwork.me`, with the FRAIM API key.
- The other inspected agent integration paths add FRAIM-named skills or commands, and the cited diagnostic code masks known secrets.
Evidence against
- Activation is through the `init-project` or `add-ide` CLI commands, not an npm install hook.
- The inspected telemetry flow concerns usage metrics; it did not show prompt text or service credentials being collected or sent.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVars
Source & flagged code
17 flagged · loading sourcedist/src/core/utils/git-utils.jsView file
9exports.sanitizeRepoIdentifier = sanitizeRepoIdentifier;
L10: const child_process_1 = require("child_process");
L11: function extractLocalFolderLabel(rawPath) {
High
Child Process
Package source references child process execution.
dist/src/core/utils/git-utils.jsView on unpkg · L9bin/fraim.jsView file
3try {
L4: require('../dist/src/cli/fraim.js');
L5: } catch (error) {
Medium
Dynamic Require
Package source references dynamic require/import behavior.
bin/fraim.jsView on unpkg · L3dist/src/first-run/session-service.jsView file
45Trigger-reachable persistence chain: manifest.bin -> bin/fraim.js -> dist/src/cli/fraim.js -> dist/src/cli/commands/first-run.js -> dist/src/first-run/session-service.js
L45: const crypto_1 = __importDefault(require("crypto"));
L46: const child_process_1 = require("child_process");
L47: const ide_detector_1 = require("../cli/setup/ide-detector");
...
L59: function getFakeStateMode() {
L60: if (process.env.FRAIM_FIRST_RUN_FAKE !== '1')
L61: return null;
...
L68: function commandVersion(command, extraBinDirs, basePath) {
L69: const executable = process.platform === 'win32' ? 'cmd.exe' : command;
L70: const args = process.platform === 'win32'
...
L83: return null;
L84: const text = `${result.stdout || ''}${result.stderr || ''}`.split(/\r?\n/)[0]?.trim() || null;
L85: return text;
Findings
1 Critical14 High5 Medium4 Low
CriticalPrevious Version Dangerous Deltadist/src/local-mcp-server/stdio-server.js
HighChild Processdist/src/core/utils/git-utils.js
HighSandbox Evasion Gated Capabilitydist/src/cli/doctor/checks/scripts-checks.js
HighTrigger Reachable Persistencedist/src/first-run/session-service.js
HighRuntime Package Installdist/src/cli/setup/user-level-sync.js
HighSemantic Analysis Limiteddist/src/cli/utils/pack-home.js#virtual:normalized:round1
HighKnown Malware Source Similarityindex.js
HighKnown Malware Source Similaritydist/src/cli/commands/override.js
HighKnown Malware Source Similaritydist/src/cli/setup/claude-code-telemetry.js
HighKnown Malware Source Similarity
Affected versions and remediation
This report applies to fraim@2.0.294.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.294 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.