registry / @factory/cli / 0.212.0
@factory/cli@0.212.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is not concrete malicious behavior because the endpoint and file scope are package-aligned. It remains suspicious because an automatic lifecycle hook downloads and activates an unverified native executable.
Static reason
One or more suspicious static signals were detected.
Trigger
npm installation that runs postinstall while the platform optional dependency is unavailable.
Impact
A compromised or substituted registry response could supply code that runs as the droid command.
Mechanism
Registry download, tar extraction, executable write, and command relinking.
AI rationale
This is not concrete malicious behavior because the endpoint and file scope are package-aligned. It remains suspicious because an automatic lifecycle hook downloads and activates an unverified native executable.
Evidence
package.jsoninstall.jsbin/droidbin/
Network endpoints1
registry.npmjs.org/
Decision evidence
public snapshotAI called this Suspicious at 86.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- A postinstall hook automatically runs install.js.
- When the optional platform package is absent, the hook fetches a registry tarball and extracts a native executable.
- The downloaded executable is written with execute permission and linked as the droid command.
- The installer does not verify the downloaded tarball against registry integrity metadata before executing the binary.
Evidence against
- The download target is the npm registry and the package name is selected from a fixed platform mapping.
- Writes and links are limited to this package's bin directory.
- The shell and child-process calls are used for CPU detection, version checking, and the package command.
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.212.0.
See all versions of @factory/cli for other recorded verdicts.
- Review the evidence and your use of @factory/cli@0.212.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.