droid@0.215.1
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe source shows a package-aligned CLI installer rather than confirmed theft or persistence, but its automatic remote native-binary fallback and permissive token-host check leave a concrete supply-chain and credential-exposure risk.
Static reason
One or more suspicious static signals were detected.
Trigger
Automatic npm postinstall when an optional platform dependency is unavailable.
Impact
A compromised or redirected package-download path could supply code executed by the droid command; the hostname check could disclose NPM_TOKEN to a lookalike host containing npmjs.org.
Mechanism
Registry fallback downloads and links a native executable.
AI rationale
The source shows a package-aligned CLI installer rather than confirmed theft or persistence, but its automatic remote native-binary fallback and permissive token-host check leave a concrete supply-chain and credential-exposure risk.
Evidence
package.jsoninstall.jsbin/droidbin/droid.backupbin/<platform binary>
Network endpoints1
registry.npmjs.org/
Decision evidence
public snapshotAI called this Suspicious at 82.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- A postinstall hook automatically runs install.js.
- The installer can download a platform binary from the npm registry and write it as an executable.
- The fallback request forwards NPM_TOKEN to any hostname containing npmjs.org.
- The hook replaces the package command shim with a linked native binary.
Evidence against
- Platform packages and versions are explicitly mapped in the manifest.
- The observed writes are limited to this package's bin directory.
- No source reads user files, modifies agent settings, or sends harvested data to a non-package service.
- The command shim executes the selected platform binary with user-supplied arguments.
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.215.1.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.215.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.