droid@0.243.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 20d ago · by lpm-firewall-aiInspected source shows a package-aligned installer fallback for platform binaries and a launcher that forwards user arguments to the selected binary. The global PATH check prints advice without modifying files; no concrete attack behavior was identified.
Static reason
One or more suspicious static signals were detected.
Trigger
Package installation, when the optional platform binary is unavailable.
Impact
The behavior sets up the CLI; no separate malicious effect was established.
Mechanism
The hook looks up the matching package version, extracts its binary into the package’s bin directory, and links the command shim to it.
AI rationale
Inspected source shows a package-aligned installer fallback for platform binaries and a launcher that forwards user arguments to the selected binary. The global PATH check prints advice without modifying files; no concrete attack behavior was identified.
Evidence
bin/droid
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines a postinstall hook and matching-version optional dependencies for the platform binaries.
- install.js uses the npm registry to look up the matching platform package version when an optional binary is missing.
- The fallback writes the extracted binary into this package’s bin directory.
- The hook links the package command to the selected binary; its global PATH helper only prints setup advice.
- The command shim selects a platform binary and forwards the caller’s arguments to it.
Evidence against
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.243.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.243.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.