registry / Credential exfiltration / @factory/cli
@factory/cli
Factory Droid CLI - AI-powered software engineering agent
This report shows the evidence for @factory/cli@1.3.0. 2 of 75 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 18h ago · by lpm-firewall-aiThe automatic postinstall fallback can send NPM_TOKEN to a non-npm host because it checks for `npmjs.org` as a substring and follows response redirects through the same helper. The intended binary download is ordinary CLI setup, but this credential disclosure path warrants blocking.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
Package installation when the platform-specific optional dependency is unavailable and NPM_TOKEN is set.
Impact
An attacker controlling the metadata response or redirect destination could receive the installer's npm token.
Mechanism
install.js requests npm package metadata, uses its tarball URL, and recursively follows redirects. The request helper sends NPM_TOKEN to any hostname containing npmjs.org, including a non-npm host with that substring.
Attack narrative
During postinstall, if the optional platform binary is missing, the script requests package metadata and follows its tarball URL and redirects. Its hostname check uses a substring match, so a deceptive non-npm hostname containing “npmjs.org” can receive NPM_TOKEN in the Authorization header. This creates an automatic credential disclosure path when the fallback runs.
AI rationale
The automatic postinstall fallback can send NPM_TOKEN to a non-npm host because it checks for `npmjs.org` as a substring and follows response redirects through the same helper. The intended binary download is ordinary CLI setup, but this credential disclosure path warrants blocking.
Evidence
package.jsoninstall.jsbin/droidbin/droid.backup
Network endpoints2
registry.npmjs.orgredirect destination supplied by the npm response
Decision evidence
public snapshotAI called this Malicious at 88.0% confidence as Malware with low false-positive risk.
Evidence for block
- The postinstall hook runs install.js automatically.
- install.js attaches NPM_TOKEN when the request hostname contains the substring npmjs.org, without checking that it is the actual npm registry host.
- The fallback obtains a tarball URL from npm metadata, then follows redirects by recursively calling the same request helper; a deceptive redirect hostname containing npmjs.org can therefore receive NPM_TOKEN.
- When the optional platform dependency is missing, the install hook automatically invokes the fallback download.
Evidence against
- The intended request destination is the official registry host registry.npmjs.org, and the token is described as helping bypass rate limits.
- The fallback downloads a platform-specific CLI binary and extracts it into the package's bin directory, consistent with the package's stated purpose.
- The script's normal Unix optimization replaces the CLI shim with a link to that binary.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetwork
Source & flagged code
9 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
8 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
HighKnown Malware Source Similarityinstall.js
HighKnown Malware Source Fingerprint Signatureinstall.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
Affected versions and remediation
This report applies to @factory/cli@1.3.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @factory/cli@1.3.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.