@factory/cli@0.237.0
Factory Droid CLI - AI-powered software engineering agent
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe postinstall behavior is package-aligned, but the fallback request can forward an existing npm token to a hostname that is not restricted to the npm registry. This conditional credential exposure warrants a warning, not a publish block.
Static reason
One or more suspicious static signals were detected.
Trigger
Postinstall runs and the optional platform binary is unavailable; NPM_TOKEN is set.
Impact
A crafted destination such as a hostname with an npmjs.org substring could receive the existing npm token.
Mechanism
The installer follows registry metadata tarball URLs and redirects, while attaching NPM_TOKEN when the requested hostname contains npmjs.org.
AI rationale
The postinstall behavior is package-aligned, but the fallback request can forward an existing npm token to a hostname that is not restricted to the npm registry. This conditional credential exposure warrants a warning, not a publish block.
Evidence
install.jspackage.json
Network endpoints1
registry.npmjs.org
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 can request a platform package tarball when the optional binary is missing.
- The installer sends NPM_TOKEN to any request hostname containing npmjs.org; the tarball URL comes from registry metadata, and redirects are followed.
- On Unix, postinstall replaces the package’s own command shim with a link to the selected binary.
Evidence against
- The manifest maps optional platform binaries to same-version @factory packages.
- The installer uses registry.npmjs.org to retrieve package metadata and performs the binary setup within the package.
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.237.0.
See all versions of @factory/cli for other recorded verdicts.
- Review the evidence and your use of @factory/cli@0.237.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.