droid@1.0.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package’s binary-download purpose is consistent with its CLI, but the installer’s permissive hostname check can send NPM_TOKEN to a foreign host selected by registry metadata. This is a credible credential exposure risk, though the source does not establish an actual malicious destination.
Static reason
One or more suspicious static signals were detected.
Trigger
Automatically during postinstall when an optional platform binary is missing, NPM_TOKEN is set, and the metadata-selected tarball hostname matches the substring check.
Impact
A crafted tarball URL such as an unrelated hostname containing `npmjs.org` could receive the npm bearer token.
Mechanism
The installer obtains the tarball URL from npm packument metadata and calls a request helper that attaches NPM_TOKEN whenever the requested hostname includes `npmjs.org`.
AI rationale
The package’s binary-download purpose is consistent with its CLI, but the installer’s permissive hostname check can send NPM_TOKEN to a foreign host selected by registry metadata. This is a credible credential exposure risk, though the source does not establish an actual malicious destination.
Evidence
package.jsoninstall.jsbin/droidbin/droid.backup
Network endpoints2
registry.npmjs.orgMetadata-selected tarball host
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The postinstall installer sends NPM_TOKEN as a Bearer credential to any request hostname containing the substring `npmjs.org`, rather than validating the hostname.
- The installer reads the binary tarball URL from npm registry metadata and requests that URL using the same request helper, allowing metadata to select a token-bearing destination that matches the substring check.
Evidence against
- The package is a platform-specific CLI wrapper that installs its native binary from npm packages.
- The initial package metadata request targets registry.npmjs.org; no unrelated collector or additional host, user, or project data is identified in the installer.
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@1.0.0.
See all versions of droid for other recorded verdicts.
- Review the evidence and your use of droid@1.0.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.