registry / Credential exfiltration / droid
droid
Factory Droid CLI - AI-powered software engineering agent
This report shows the evidence for droid@1.3.0. 1 of 77 known versions is blocked or flagged. See all versions.
AI Security Review
scanned 18h ago · by lpm-firewall-aiThe automatic install fallback sends NPM_TOKEN based on a substring hostname check and uses a tarball URL supplied by package metadata. This creates a concrete path for disclosing npm credentials to a lookalike host.
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
During postinstall, the platform binary is missing from optional dependencies and NPM_TOKEN is set.
Impact
A crafted tarball URL using a lookalike hostname can capture the user's npm token.
Mechanism
install.js reads the fallback tarball URL from npm metadata and sends the token in the Authorization header when the URL hostname contains the substring “npmjs.org”; the URL is not restricted to the registry host.
Attack narrative
The postinstall hook falls back to downloading a platform binary when an optional dependency is missing. It reads the tarball URL from npm metadata, then makeRequest attaches NPM_TOKEN to any hostname containing “npmjs.org.” A crafted lookalike hostname can therefore receive the token during installation.
AI rationale
The automatic install fallback sends NPM_TOKEN based on a substring hostname check and uses a tarball URL supplied by package metadata. This creates a concrete path for disclosing npm credentials to a lookalike host.
Evidence
package.jsoninstall.jsbin/droidbin/droid.backup
Network endpoints2
registry.npmjs.orgtarball URL supplied by npm package metadata (host not restricted)
Decision evidence
public snapshotAI called this Malicious at 94.0% confidence as Malware with low false-positive risk.
Evidence for block
- The postinstall hook runs install.js automatically.
- When NPM_TOKEN is set, install.js attaches it as a Bearer token to any request whose hostname contains “npmjs.org,” rather than checking that the hostname is the npm registry.
- The fallback download takes its tarball URL from npm package metadata and requests it through the same function, allowing a crafted hostname such as evilnpmjs.org to receive NPM_TOKEN.
Evidence against
- The fallback download runs only when the platform binary is missing from optional dependencies.
- The intended install behavior is to download the platform-specific CLI binary from npm and link it into the package.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
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 droid@1.3.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing droid@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.