droid@0.193.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is a package-aligned CLI installer rather than concrete malicious behavior, but its install-time remote native payload path lacks integrity verification. Warn rather than block.
Static reason
One or more suspicious static signals were detected.
Trigger
npm installation with lifecycle scripts enabled and missing platform optional dependency
Impact
A tampered or substituted registry response could execute native code during installation.
Mechanism
unverified remote native-binary fallback and install-time execution
AI rationale
This is a package-aligned CLI installer rather than concrete malicious behavior, but its install-time remote native payload path lacks integrity verification. Warn rather than block.
Evidence
package.jsoninstall.jsplatform.jsbin/droidbin/droid.backup
Network endpoints1
registry.npmjs.org/
Decision evidence
public snapshotAI called this Suspicious at 89.0% confidence as Critical Vulnerability with low false-positive risk.
Evidence for warning
- package.json runs `node install.js` at postinstall.
- install.js fetches platform tarballs from registry.npmjs.org and writes an executable.
- Downloaded tarball integrity is not checked before extraction/execution.
- postinstall validates the selected native binary with `--version`.
Evidence against
- Network fallback is limited to declared @factory platform packages.
- Installer changes only this package's bin shim; no user profile or agent-config writes.
- bin/droid only launches the selected platform binary on explicit CLI use.
- No credential harvesting or non-npm exfiltration found.
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.193.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.193.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.