@factory/cli@0.188.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe lifecycle behavior is package-aligned and confined to the CLI's own binary path, so there is no evidence of intentional malware. However, install-time download and execution of an integrity-unverified native payload is a real unresolved supply-chain risk.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall when the optional platform dependency is unavailable
Impact
A compromised registry response or redirected tarball could cause native code execution during installation.
Mechanism
registry-driven native-binary download, local write, and execution
AI rationale
The lifecycle behavior is package-aligned and confined to the CLI's own binary path, so there is no evidence of intentional malware. However, install-time download and execution of an integrity-unverified native payload is a real unresolved supply-chain risk.
Evidence
package.jsoninstall.jsplatform.jsbin/droidbin/droid.backup
Network endpoints1
registry.npmjs.org/
Decision evidence
public snapshotAI called this Suspicious at 86.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- package.json runs `node install.js` as postinstall.
- install.js fetches a platform tarball from registry metadata and writes its native binary.
- install.js executes the downloaded/resolved binary with `--version` during installation.
- Redirects and downloaded tarball content are not integrity-verified in install.js.
Evidence against
- Downloads are limited by source construction to npm registry metadata for package-owned @factory/cli platform packages.
- NPM_TOKEN is only attached when the current request hostname includes npmjs.org.
- Postinstall modifies only this package's bin/droid shim and local bin binary.
- No source evidence of credential harvesting, exfiltration, broad file writes, agent-config mutation, or destructive actions.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
8 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 High5 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
HighTrigger Reachable Persistenceinstall.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistenceinstall.js
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to @factory/cli@0.188.0.
See all versions of @factory/cli for other recorded verdicts.
- Review the evidence and your use of @factory/cli@0.188.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.