droid@0.231.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe inspected lifecycle and launcher implement transparent platform binary setup consistent with the package's CLI function. No concrete exfiltration, malicious persistence, agent control hijacking, or lifecycle self-dependency chain was established.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall sets up the binary; invoking droid launches it.
Impact
Package-local executable setup and ordinary CLI execution; no concrete malicious impact was established.
Mechanism
The installer resolves or downloads a platform binary, links its package-local shim, and optionally checks the binary version.
AI rationale
The inspected lifecycle and launcher implement transparent platform binary setup consistent with the package's CLI function. No concrete exfiltration, malicious persistence, agent control hijacking, or lifecycle self-dependency chain was established.
Evidence
bin/droid
Network endpoints1
registry.npmjs.org/${encodedName}
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json runs install.js after installation and declares version-matched Factory platform dependencies, without a runtime self-dependency.
- install.js locates the platform binary and replaces its own bin/droid shim with a link.
- Fallback downloads begin at registry.npmjs.org; npm token authentication is conditional on the destination hostname containing npmjs.org.
- bin/droid launches the selected binary with caller arguments and inherited terminal streams.
- platform.js resolves platform dependency binaries; its system commands detect CPU capabilities.
- Install-time binary execution uses the --version argument with a timeout.
Evidence against
- Downloaded and optional dependency binaries are outside this snapshot and were not inspected.
- The npm authentication hostname check uses substring matching rather than an exact host allowlist, but no attacker-controlled destination was established.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetwork
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.231.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.231.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.