@factory/cli@0.240.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 23d ago · by lpm-firewall-aiThe fallback sends NPM_TOKEN using a hostname substring check and follows redirects through the same function, leaving the credential destination insufficiently restricted. The package-specific binary download is otherwise consistent with the CLI’s declared optional dependencies, so this supports a warning rather than a block.
Static reason
One or more suspicious static signals were detected.
Trigger
The package postinstall runs, its platform binary is unavailable, and NPM_TOKEN is set.
Impact
A destination outside the intended npm registry could receive the npm token if the returned tarball URL or a redirect uses a matching hostname.
Mechanism
The fallback requests a tarball URL from npm metadata; makeRequest attaches the bearer token based on a substring match in the hostname and reuses that function for redirects.
AI rationale
The fallback sends NPM_TOKEN using a hostname substring check and follows redirects through the same function, leaving the credential destination insufficiently restricted. The package-specific binary download is otherwise consistent with the CLI’s declared optional dependencies, so this supports a warning rather than a block.
Evidence
package.jsoninstall.js
Network endpoints1
registry.npmjs.org/${encodedName}
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The postinstall hook runs install.js and declares same-version platform binary packages as optional dependencies.
- The install script downloads a platform binary only when the optional dependency is missing, using the package tarball URL returned by npm metadata.
- When NPM_TOKEN is set, requests to any hostname containing “npmjs.org” receive it as a bearer token.
- Redirects are followed by calling the same request function again, so the hostname check also applies to redirect destinations.
Evidence against
- The fallback looks up a platform-specific package at the CLI’s own version through registry.npmjs.org, which is consistent with installing the CLI’s native binary.
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 @factory/cli@0.240.0.
See all versions of @factory/cli for other recorded verdicts.
- Review the evidence and your use of @factory/cli@0.240.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.