@prefactor/cli@0.5.1
Prefactor command-line interface
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package's login flow sends the machine hostname and platform to its default service without documenting that collection. Since this occurs only during an explicit login command, classify it as suspicious telemetry rather than malicious exfiltration.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs `prefactor login`.
Impact
The service receives the user's machine hostname and platform during authentication.
Mechanism
The CLI reads the hostname, platform, and version, then POSTs them as JSON to the configured Prefactor API.
AI rationale
The package's login flow sends the machine hostname and platform to its default service without documenting that collection. Since this occurs only during an explicit login command, classify it as suspicious telemetry rather than malicious exfiltration.
Evidence
dist/index.cjsprefactor.json
Network endpoints1
app.prefactorai.com
Decision evidence
public snapshotAI called this Suspicious at 86.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- Running `prefactor login` starts the device login flow.
- The login flow POSTs client information to the configured Prefactor API.
- That information includes the CLI version, platform, and the machine's hostname.
- The default API host is app.prefactorai.com.
Evidence against
- The manifest defines no install lifecycle scripts.
- The identifying data is sent only when a user runs the login command.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystem
HighEntropyStringsUrlStrings
Source & flagged code
8 flaggeddist/install/platform.jsView file
1import { execFileSync } from 'node:child_process';
L2: function normalizePlatform(platform) {
High
Child Process
Package source references child process execution.
dist/install/platform.jsView on unpkg · L1dist/bin/cli.cjsView file
495Cross-file remote execution chain: dist/bin/cli.cjs spawns dist/bin/cli.js; helper contains network access plus dynamic code execution.
L495: var import_commander11 = require("commander");
L496: // packages/cli/package.json
L497: var package_default = {
...
L526: type: "git",
L527: url: "git+https://github.com/prefactordev/typescript-sdk.git",
L528: directory: "packages/cli"
...
L558: method: "PUT",
L559: body: { details }
L560: });
...
L694: async function findConfigPath() {
L695: const directoryRoot = await findDirectoryRoot(process.cwd());
L696: const directoryRootConfigPath = import_node_path.resolve(directoryRoot, CONFIG_FILENAME);
High
Cross File Remote Execution Context
Source spawns a local helper that also contains network and dynamic execution context; review data flow before blocking.
dist/bin/cli.cjsView on unpkg · L495Findings
1 Critical2 High6 Medium3 Low
CriticalPrevious Version Dangerous Deltadist/index.cjs
HighChild Processdist/install/platform.js
HighCross File Remote Execution Contextdist/bin/cli.cjs
MediumEnvironment Vars
MediumAi Review Evidencedist/index.cjs
MediumAi Review Evidencedist/index.cjs
MediumAi Review Evidencedist/index.cjs
MediumAi Review Evidencedist/index.cjs
MediumAi Review Evidencedist/index.cjs
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @prefactor/cli@0.5.1.
See all versions of @prefactor/cli for other recorded verdicts.
- Review the evidence and your use of @prefactor/cli@0.5.1 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.