droid@0.220.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe postinstall behavior is a conventional platform-binary installer confined to the package directory. Static inspection found no concrete exfiltration, persistence, destructive action, or foreign control-surface mutation.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall triggers the installer.
Impact
No confirmed attack impact; changes are limited to the installed package command.
Mechanism
The installer obtains the selected platform binary and links or writes the package's own droid command.
AI rationale
The postinstall behavior is a conventional platform-binary installer confined to the package directory. Static inspection found no concrete exfiltration, persistence, destructive action, or foreign control-surface mutation.
Evidence
bin/droid
Network endpoints1
registry.npmjs.org/
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package runs install.js only as a postinstall hook and declares platform-specific Factory CLI optional dependencies.
- The installer selects a platform binary and, if absent, downloads the matching package version from the npm registry.
- Installer writes are confined to its own bin directory and replace only its droid command shim.
- No source code inspected harvests files, exports credentials, alters agent settings, or modifies consumer project files.
Evidence against
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.220.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.220.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.