registry / @factory/cli / 0.230.0
@factory/cli@0.230.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe inspected executable source supports an ordinary platform binary installer and launcher, with no concrete malicious chain. The weak hostname check and unavailable dependency binaries do not establish an active attack in this snapshot.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall sets up the binary; invoking droid launches it.
Impact
Package-local executable setup and execution were established; malicious credential export, persistence, and broad project mutation were not established.
Mechanism
The installer resolves or downloads a matching Factory binary, updates its own shim, and checks the binary version.
AI rationale
The inspected executable source supports an ordinary platform binary installer and launcher, with no concrete malicious chain. The weak hostname check and unavailable dependency binaries do not establish an active attack in this snapshot.
Evidence
bin/droid
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json runs install.js after installation and pins Factory platform dependencies to the same release; no runtime self-dependency is present.
- install.js targets the package-local bin/droid shim and replaces it with a link to the selected binary.
- Fallback downloads begin at registry.npmjs.org for the selected platform package and version.
- NPM_TOKEN is used for npm download authentication; no operator-configured credential destination is exposed.
- platform.js resolves platform package binaries, and bin/droid executes the selected binary with caller arguments.
Evidence against
- Downloaded platform binaries are outside this snapshot and cannot be assessed here.
- The npm authentication hostname check uses substring matching rather than an exact hostname allowlist.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
7 flaggedpackage.jsonView file
•scripts.postinstall = node install.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg9scripts.postinstall = node install.js
Install-time code downloads an unverified remote native executable, stages it locally, activates an executable path, and exposes it to process execution.
L9: *
L10: * Based on esbuild's approach: https://github.com/evanw/esbuild/pull/1621
L11: * and Sentry's guide: https://sentry.engineering/blog/publishing-binaries-on-npm
L12: *
...
L19: const path = require('path');
L20: const https = require('https');
L21: const zlib = require('zlib');
...
L27: getBinaryName,
L28: getBinaryPath,
L29: detectAVX2Support,
...
L50:
L51: function validateBinaryVersion(binaryPath) {
High
Unverified Remote Native Payload Install
Install-time source downloads a native archive from a fixed external host without transport verification, extracts it, and installs an executable payload.
package.jsonView on unpkg · L9•scripts.postinstall = node install.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
Findings
6 High4 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processinstall.js
HighShellinstall.js
HighSame File Env Network Executioninstall.js#virtual:normalized:round1
HighUnverified Remote Native Payload Installpackage.json
HighSemantic Analysis Limitedinstall.js#virtual:normalized:round1
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Low
Affected versions and remediation
This report applies to @factory/cli@0.230.0.
See all versions of @factory/cli for other recorded verdicts.
- Review the evidence and your use of @factory/cli@0.230.0 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.