droid@0.188.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe lifecycle behavior is package-aligned binary bootstrapping, not confirmed malicious intent. Nevertheless, the unverified network-delivered native executable is run during install, so it warrants a warning.
Static reason
One or more suspicious static signals were detected.
Trigger
npm installation with lifecycle scripts enabled and no resolved platform optional dependency
Impact
A registry-delivered native binary may execute during installation.
Mechanism
registry tarball download, native binary extraction, local executable replacement and version invocation
AI rationale
The lifecycle behavior is package-aligned binary bootstrapping, not confirmed malicious intent. Nevertheless, the unverified network-delivered native executable is run during install, so it warrants a warning.
Evidence
package.jsoninstall.jsplatform.jsbin/droidbin/droid.backup
Network endpoints1
registry.npmjs.org/
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- postinstall runs install.js.
- Fallback downloads a platform tarball, extracts bin/droid, and chmod-writes it.
- install.js executes the resulting binary with --version.
- No checksum or signature validation is implemented for the downloaded tarball.
Evidence against
- Download is a fallback for declared @factory/cli-* optional dependencies.
- Registry lookup is pinned to the package version and uses HTTPS.
- Filesystem mutation is confined to this package's bin/droid shim and backup.
- PATH/profile logic only prints remediation commands; it does not modify user profiles.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
8 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 High5 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
HighTrigger Reachable Persistenceinstall.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistenceinstall.js
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to droid@0.188.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.188.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.