fraim@2.0.348
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiSource inspection found no npm lifecycle hook or confirmed malicious behavior. The flagged telemetry setup is tied to explicit CLI setup commands and uses a loopback receiver, so the package is clean.
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
A user runs add-ide or init-project with Claude Code detected.
Impact
The inspected path did not show those metrics being sent to an external recipient or establish another concrete attack effect.
Mechanism
The setup adds telemetry settings to the user's Claude configuration; the MCP server starts a local metrics receiver.
AI rationale
Source inspection found no npm lifecycle hook or confirmed malicious behavior. The flagged telemetry setup is tied to explicit CLI setup commands and uses a loopback receiver, so the package is clean.
Evidence
~/.claude/settings.json
Decision evidence
public snapshotAI called this Clean at 80.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines CLI entrypoints and has no npm lifecycle scripts.
- Claude token telemetry is enabled by add-ide or init-project; it writes user settings, and its receiver binds to loopback.
- The inspected source did not establish credential theft, remote payload execution, destructive behavior, or another concrete attack.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
16 flagged · loading sourcedist/registry/scripts/learning/run-publication.jsView file
9const node_path_1 = __importDefault(require("node:path"));
L10: const node_child_process_1 = require("node:child_process");
L11: const proposal_queue_1 = require("./proposal-queue");
High
Child Process
Package source references child process execution.
dist/registry/scripts/learning/run-publication.jsView on unpkg · L9dist/src/cli/doctor/checks/scripts-checks.jsView file
235// Primary probe: py launcher (not subject to App Execution Alias)
L236: const pyResult = (0, child_process_1.spawnSync)('py --version', { timeout: 1500, encoding: 'utf8', shell: true, windowsHide: true });
L237: if (pyResult.status === 0) {
High
Shell
Package source references shell execution.
dist/src/cli/doctor/checks/scripts-checks.jsView on unpkg · L235bin/fraim.jsView file
Findings
1 Critical13 High5 Medium4 Low
CriticalPrevious Version Dangerous Deltadist/src/cli/doctor/checks/mcp-connectivity-checks.js
HighChild Processdist/registry/scripts/learning/run-publication.js
HighShelldist/src/cli/doctor/checks/scripts-checks.js
HighSandbox Evasion Gated Capabilitydist/src/cli/commands/override.js
HighTrigger Reachable Persistencedist/src/cli/utils/persist-shell-path.js
HighRuntime Package Installdist/src/cli/setup/user-level-sync.js
HighSemantic Analysis Limiteddist/src/cli/utils/managed-agent-install.js#virtual:normalized:round1
HighKnown Malware Source Similarityindex.js
HighKnown Malware Source Similaritydist/src/cli/commands/override.js
HighKnown Malware Source Similarity
Affected versions and remediation
This report applies to fraim@2.0.348.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.348 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.