The update checker can forward NPM_TOKEN to an arbitrary configured HTTP(S) registry without validating the destination host, creating a credential disclosure risk when configuration is untrusted. The source shows the check behind an internal worker argument and did not show ordinary CLI startup invoking it, so this warrants a warning rather than a publish block.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Invoking the CLI with its internal --fxri-update-check-worker argument runs the update check. No call to its background-spawn function from ordinary CLI startup was identified.
Impact
If the selected registry URL is controlled by an untrusted project or configuration source, the npm token may be disclosed to that host.
Mechanism
The checker selects a configurable HTTP(S) registry, returns NPM_TOKEN without host validation, and attaches it as a Bearer token to a request for the package’s latest-version metadata.
Evidence
dist/cli.jspackage.json.toolkitrc.json.npmrc.toolkit-update-check.json