@factory/cli@0.242.1
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe fallback's token forwarding uses a weak hostname check and follows metadata-provided URLs, creating a conditional credential exposure risk. The source does not establish an active third-party recipient, so this warrants a warning rather than a block.
Static reason
One or more suspicious static signals were detected.
Trigger
The package is installed with lifecycle scripts enabled, the platform binary is missing from optional dependencies, and NPM_TOKEN is set.
Impact
A qualifying metadata URL or redirect could disclose the npm bearer token to a non-registry host.
Mechanism
The installer fetches registry metadata, requests its returned tarball URL, and follows redirects. Its token check uses a hostname substring test.
AI rationale
The fallback's token forwarding uses a weak hostname check and follows metadata-provided URLs, creating a conditional credential exposure risk. The source does not establish an active third-party recipient, so this warrants a warning rather than a block.
Evidence
package.jsoninstall.js
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Suspicious at 87.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The postinstall hook runs the installer, and platform binaries are declared as same-version optional dependencies.
- The fallback installer adds NPM_TOKEN to requests when the hostname contains npmjs.org, rather than matching an exact trusted host.
- The installer follows redirects and obtains the tarball URL from registry metadata, then requests that URL using the same helper.
- The fallback runs when the platform binary is missing from optional dependencies.
Evidence against
- The fallback fetches metadata from registry.npmjs.org for a platform package selected by the installer.
- The fallback is conditional on the optional platform binary being unavailable.
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.242.1.
See all versions of @factory/cli for other recorded verdicts.
- Review the evidence and your use of @factory/cli@0.242.1 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.