droid@0.189.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe installer is package-aligned and does not alter foreign agent or shell configuration, but it installs an unverified remote native payload at lifecycle time. This warrants a warning rather than a block.
Static reason
One or more suspicious static signals were detected.
Trigger
npm installation when the platform optional dependency is unavailable
Impact
A compromised or substituted registry-delivered binary could execute during installation validation and later through the droid command.
Mechanism
downloads and installs an unverified native binary from npm registry metadata
AI rationale
The installer is package-aligned and does not alter foreign agent or shell configuration, but it installs an unverified remote native payload at lifecycle time. This warrants a warning rather than a block.
Evidence
package.jsoninstall.jsplatform.jsbin/droidbin/droid.backupbin/droid.exe
Network endpoints1
registry.npmjs.org/
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- package.json runs postinstall via install.js.
- install.js fetches a platform tarball from registry.npmjs.org when optional dependencies are absent.
- install.js extracts package/bin/droid and writes it executable without integrity verification.
- postinstall replaces bin/droid with a link to the downloaded or optional-dependency native binary.
Evidence against
- Network fallback is limited to npm registry package retrieval.
- NPM_TOKEN is attached only when the request hostname includes npmjs.org.
- Shell-profile content is printed as a suggestion; no profile or agent configuration is written.
- No credential harvesting, broad filesystem traversal, exfiltration, or AI-agent control-surface mutation found.
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 droid@0.189.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.189.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.