droid@0.196.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe flagged primitives implement a conventional package-local native CLI bootstrap. The source does not establish exfiltration, remote code execution beyond the selected CLI binary, persistence outside the package, or AI-agent control-surface mutation.
Static reason
One or more suspicious static signals were detected.
Trigger
npm install when the platform optional dependency is unavailable
Impact
A platform binary can be installed and executed when the user runs droid.
Mechanism
npm-registry binary fallback and package-local shim linking
AI rationale
The flagged primitives implement a conventional package-local native CLI bootstrap. The source does not establish exfiltration, remote code execution beyond the selected CLI binary, persistence outside the package, or AI-agent control-surface mutation.
Evidence
package.jsoninstall.jsplatform.jsbin/droidbin/droid.backupbin/droid.exe
Network endpoints1
registry.npmjs.org/
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with medium false-positive risk.
Evidence for AI clean decision
- postinstall can fetch a platform binary from the npm registry fallback and write it under bin/.
- The fallback tarball is selected from registry metadata without an in-source integrity check.
Evidence against
- The lifecycle hook only invokes the package-local installer.
- The requested package name is selected from fixed same-vendor optional dependencies.
- File mutation is limited to replacing this package's bin/droid shim with its platform binary.
- NPM_TOKEN is sent only when the request hostname includes npmjs.org.
- No source reads user credentials/files, writes agent configuration, or contacts non-registry endpoints.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
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
HighShellinstall.js
HighSame File Env Network Executioninstall.js#virtual:normalized:round1
HighUnverified Remote Native Payload Installpackage.json
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.196.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.196.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.