droid@0.212.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is package-aligned CLI installation behavior, not evidence of deliberate theft or persistence, but it creates an unresolved install-time remote native-code execution path without source-level integrity verification.
Static reason
One or more suspicious static signals were detected.
Trigger
npm installation when the matching optional dependency is unavailable.
Impact
A compromised or substituted registry response could cause native code to run with installer permissions.
Mechanism
Registry metadata fetch, redirect-following binary download, local write, and version-command execution.
AI rationale
This is package-aligned CLI installation behavior, not evidence of deliberate theft or persistence, but it creates an unresolved install-time remote native-code execution path without source-level integrity verification.
Evidence
package.jsoninstall.jsbin/droidbin/droid.backup
Network endpoints1
registry.npmjs.org/
Decision evidence
public snapshotAI called this Suspicious at 87.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- Its postinstall hook downloads a platform binary when the optional dependency is absent.
- The installer accepts a registry-provided tarball URL, follows redirects, writes the binary, and runs it during installation.
- The downloaded binary is not integrity-checked by this source.
Evidence against
- The download target is a fixed, version-matched Factory platform package from the npm registry.
- Writes are limited to this package's bin directory; no credential harvesting, project mutation, or agent-control changes were found.
- The command shim only launches the selected platform binary when the user invokes droid.
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 droid@0.212.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@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.