droid@0.217.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is a transparent, package-aligned native CLI installer with a registry fallback, not a concrete malicious chain. It does not mutate foreign control surfaces or show collection, exfiltration, destructive behavior, or remote code selection beyond fixed platform packages.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall, when the platform optional dependency is unavailable
Impact
Installs or links the package's platform-specific droid executable.
Mechanism
package-local native CLI binary retrieval and shim linking
AI rationale
This is a transparent, package-aligned native CLI installer with a registry fallback, not a concrete malicious chain. It does not mutate foreign control surfaces or show collection, exfiltration, destructive behavior, or remote code selection beyond fixed platform packages.
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook runs an installer that can download a platform-specific native binary from npm.
- The fallback writes the downloaded binary into this package's bin directory and links the droid shim to it.
- The installer forwards NPM_TOKEN only to npmjs.org registry requests.
Evidence against
- The downloaded package names are fixed same-vendor platform packages at the package version.
- Network use is limited to retrieving the npm registry packument and its selected tarball.
- No source code harvests files or credentials, modifies shell profiles, or writes AI-agent configuration.
- The command shim executes only the resolved platform binary with user-supplied arguments.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
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.217.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@0.217.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.