@factory/cli@0.216.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is a package-aligned binary installer, not confirmed malware, but it automatically executes a remotely fetched native payload without source-level integrity verification. That warrants a warning rather than a block.
Static reason
One or more suspicious static signals were detected.
Trigger
npm runs postinstall when the platform optional dependency is unavailable.
Impact
A compromised or substituted registry-delivered binary could execute with the installer's privileges.
Mechanism
downloads, extracts, marks executable, links, and version-runs a platform binary
AI rationale
This is a package-aligned binary installer, not confirmed malware, but it automatically executes a remotely fetched native payload without source-level integrity verification. That warrants a warning rather than a block.
Evidence
package.jsoninstall.jsbin/droidbin/droid.backupbin/droid.exe
Network endpoints1
registry.npmjs.org/${encodedName}
Decision evidence
public snapshotAI called this Suspicious at 85.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The automatic postinstall hook downloads a platform binary from registry metadata when optional dependencies are absent.
- The downloaded archive is extracted and written as an executable without a checksum or signature check.
- The installer then runs the selected binary during installation to query its version.
Evidence against
- Downloads are limited to the npm registry and exact same-version, same-vendor platform packages.
- Filesystem changes are scoped to this package's bin directory and replace only its droid shim.
- The token is attached only when the requested host contains npmjs.org; no source shows data exfiltration or foreign configuration writes.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
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.216.0.
See all versions of @factory/cli for other recorded verdicts.
- Review the evidence and your use of @factory/cli@0.216.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.