registry / @factory/cli / 0.234.0
@factory/cli@0.234.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 29d ago · by lpm-firewall-aiThe inspected lifecycle and entrypoints implement package-aligned native CLI installation and execution. Download integrity and hostname-validation weaknesses do not establish a concrete attack in the inspected call chain.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall performs binary setup; invoking droid launches the selected CLI binary.
Impact
Package-local executable installation and CLI execution; no concrete credential exfiltration, broad project mutation, or agent control hijacking was established.
Mechanism
The installer resolves matching Factory dependencies, falls back to HTTPS npm downloads, and modifies its own executable shim.
AI rationale
The inspected lifecycle and entrypoints implement package-aligned native CLI installation and execution. Download integrity and hostname-validation weaknesses do not establish a concrete attack in the inspected call chain.
Evidence
bin/droidbin/droid.backup
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json runs install.js after installation and declares matching-version Factory platform dependencies, without a runtime self-dependency.
- install.js obtains the selected platform release from registry.npmjs.org and downloads its tarball.
- install.js writes the extracted executable into its own bin directory and replaces its own CLI shim.
- NPM_TOKEN authentication is gated by the request hostname; the inspected callers use npm registry metadata rather than an operator-configured endpoint.
- platform.js resolves platform executables; bin/droid launches the selected executable with caller arguments.
Evidence against
- The fallback download lacks archive integrity verification and executes the binary for version validation.
- The npm authentication hostname check uses substring matching, which is weaker than an exact hostname allowlist.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
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.234.0.
See all versions of @factory/cli for other recorded verdicts.
- Review the evidence and your use of @factory/cli@0.234.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.