pnpm expands ${...} environment-variable placeholders in the httpProxy, httpsProxy, noProxy, proxy and noproxy settings when those settings come from a project's pnpm-workspace.yaml, which is repository-controlled and therefore untrusted. getOptionsFromPnpmSettings guarded only the registry field via REQUEST_DESTINATION_SCALAR_KEYS, so a malicious repository can route install requests through an attacker-controlled proxy whose URL embeds an environment secret and exfiltrate it before any lifecycle script runs (--ignore-scripts is no defence). Fixed in 10.34.5 and 11.11.0 by adding the proxy fields to the guarded set.