[BUG] npm I fails due to IP address being used to connect

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

When I run npm i after getting the packages it then spits out

npm ERR! code ETIMEDOUT
npm ERR! syscall connect
npm ERR! errno ETIMEDOUT
npm ERR! network request to http://192.168.3.117/value-equal/-/value-equal-1.0.1.tgz failed, reason: connect ETIMEDOUT 192.168.3.117:80
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

• I am not using the 192.168.3.X subnet
• No Proxy was set
• No Proxy is in use
  I have thus far 0 ideas how to fix or find where it is pulling that IP address from

Expected Behavior

It to connect to the normal npm.com domain and download the package

Steps To Reproduce

1. Run npm i

Environment

• npm: 8.5.5
• Node.js: v17.9.0
• OS Name: Windows
• System Model Name: 11
• npm config:

; "user" config from C:\Users\Lagicrus\.npmrc

registry = "https://registry.npmjs.org/"

; node bin location = C:\Program Files\nodejs\node.exe
; cwd = E:\GitHub\project
; HOME = C:\Users\Lagicrus
; Run `npm config ls -l` to show all defaults.

Start by reproducing npm i on Windows with npm 8.5.5 and Node.js v17.9.0, then inspect the reported package URL alongside the shown npm config output. Done means identifying why the request uses 192.168.3.117 and making installation connect to the configured https://registry.npmjs.org/ domain.