droid@0.241.1
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 22d ago · by lpm-firewall-aiThe lifecycle hook and native binary download are part of this CLI's platform-specific installation flow. The conditional npm token handling and redirect behavior merit attention, but the inspected code does not establish an unrelated credential recipient or a concrete attack.
Static reason
One or more suspicious static signals were detected.
Trigger
Package installation, with the download fallback activated only if the optional binary is missing.
Impact
The inspected behavior sets up the CLI; no unrelated system mutation or confirmed malicious transfer was found.
Mechanism
The installer requests package metadata and a platform tarball from npm's registry, then links the selected binary into the package's own command path.
AI rationale
The lifecycle hook and native binary download are part of this CLI's platform-specific installation flow. The conditional npm token handling and redirect behavior merit attention, but the inspected code does not establish an unrelated credential recipient or a concrete attack.
Evidence
bin/droid
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json runs a postinstall hook and declares version-matched platform binary dependencies.
- The fallback request starts at npm's registry; it forwards NPM_TOKEN only when the request hostname contains npmjs.org.
- The fallback runs only when the optional binary is missing, and the installer links the binary into this package's own command shim.
Evidence against
- The token hostname check uses a substring match and redirects are followed, but the inspected code does not show a package-selected unrelated recipient.
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.241.1.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.241.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.