droid@0.218.1
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe install-time native-binary fallback is a real supply-chain primitive, but its scoped, pinned registry retrieval and package-local setup match this CLI's declared platform dependency design. Static source inspection found no concrete malicious behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
npm installation runs the postinstall hook.
Impact
It can download, write, and validate the declared platform CLI binary, but inspected code shows no exfiltration or broad persistence.
Mechanism
Package-local native binary installation and shim optimization.
AI rationale
The install-time native-binary fallback is a real supply-chain primitive, but its scoped, pinned registry retrieval and package-local setup match this CLI's declared platform dependency design. Static source inspection found no concrete malicious behavior.
Evidence
bin/droidbin/droid.backupbin/droid.exe
Network endpoints1
registry.npmjs.org/
Decision evidence
public snapshotAI called this Clean at 87.0% confidence as Benign with medium false-positive risk.
Evidence for AI clean decision
- The automatic postinstall hook runs install.js.
- When its optional platform package is absent, the hook downloads and writes a native executable.
- The hook replaces its own bin/droid shim with a link to that executable and invokes it only with --version.
Evidence against
- The fallback requests the npm registry for a pinned, same-vendor platform package version.
- The NPM token header is restricted to npmjs.org requests.
- Writes are limited to this package's bin directory; no credential harvesting, project-wide mutation, or agent-control writes appear in the inspected source.
- The executable launch is the declared droid command path and is limited to version validation during installation.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetwork
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
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
LowNo License
Affected versions and remediation
This report applies to droid@0.218.1.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.218.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.