droid@0.211.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe source is a transparent platform-binary launcher, not direct evidence of malicious intent. Its automatic download and execution of an unchecked native payload nevertheless leaves a meaningful supply-chain risk.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing the package when its platform optional dependency is unavailable; the postinstall hook runs automatically.
Impact
A compromised registry record or tarball could cause native code to run during installation.
Mechanism
Registry-selected native binary download, write, link, and execution.
AI rationale
The source is a transparent platform-binary launcher, not direct evidence of malicious intent. Its automatic download and execution of an unchecked native payload nevertheless leaves a meaningful supply-chain risk.
Evidence
package.jsoninstall.jsbin/droidbin/droid.exebin/droid.backup
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Suspicious at 86.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package runs install.js automatically after installation.
- The installer obtains a registry-selected native tarball without checking an integrity value.
- It writes the extracted executable into its own bin directory and invokes it during installation.
Evidence against
- The only fixed network host is the npm registry, and the requested packages are fixed same-vendor platform packages at the package version.
- The token header is limited to npmjs.org requests; no general environment harvesting or non-registry exfiltration appears in the inspected source.
- Filesystem changes are limited to this package's command shim and binary files; no project, shell-profile, or agent-control files are modified.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
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.211.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.211.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.