@factory/cli@0.194.1
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 3mo ago · by lpm-firewall-aiNo concrete exfiltration, persistence outside the package, or AI-agent control-surface modification was found. The unverified install-time native payload path is a real unresolved supply-chain risk and warrants a warning.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall when the platform optional dependency is missing
Impact
A compromised or substituted registry response could place an unverified native executable in the package CLI path.
Mechanism
registry-mediated native-binary download, extraction, and executable shim replacement
AI rationale
No concrete exfiltration, persistence outside the package, or AI-agent control-surface modification was found. The unverified install-time native payload path is a real unresolved supply-chain risk and warrants a warning.
Evidence
package.jsoninstall.jsplatform.jsbin/droidbin/droid.backup
Network endpoints1
registry.npmjs.org/
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- Postinstall downloads a platform binary when optional dependencies are absent.
- The downloaded tarball URL is registry-supplied and is extracted without an integrity check.
- Postinstall replaces the CLI shim with, and executes version checks on, the native binary.
Evidence against
- Network access is limited to the npm registry path for this package's declared platform dependencies.
- No source evidence of credential exfiltration, broad filesystem harvesting, agent-config mutation, or destructive behavior.
- CLI execution is user-invoked and targets the selected platform binary.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
6 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
5 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
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @factory/cli@0.194.1.
See all versions of @factory/cli for other recorded verdicts.
- Review the evidence and your use of @factory/cli@0.194.1 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.