The package’s fallback install path routes dependency requests to registry.npmmirror.com and passes through environment variables that may carry npm credentials. The source does not prove Bun sends those credentials to the mirror, so this warrants a warning as a credential-handling vulnerability rather than a block.
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
An invoked release flow installs dependencies when no registry override is set and a retry selects the mirror.
Impact
If Bun uses an environment token for authentication with the selected mirror, that credential could be disclosed to the mirror operator.
Mechanism
The code selects registry.npmmirror.com as a fallback and passes most of process.env to the Bun install subprocess, excluding registry override variables but not token variables.
Network endpoints2
registry.npmmirror.com/registry.npmjs.org/