The NPM registry blocks TOR IPs. What is the best way to evade this?

I want to make progress while using tailsOS, but NPM will not accept tor IPs. How should I evade this? Is there a general-guide on how to evade these anti-spam efforts?

npm ERR! code ECONNREFUSED
npm ERR! errno ECONNREFUSED
npm ERR! FetchError: request to https://registry.npmjs.org/react failed, reason: 
npm ERR!     at ClientRequest.<anonymous> (/usr/share/nodejs/minipass-fetch/lib/index.js:130:14)
npm ERR!     at ClientRequest.emit (node:events:524:28)
npm ERR!     at emitErrorEvent (node:_http_client:101:11)
npm ERR!     at TLSSocket.socketErrorListener (node:_http_client:504:5)
npm ERR!     at TLSSocket.emit (node:events:536:35)
npm ERR!     at emitErrorNT (node:internal/streams/destroy:169:8)
npm ERR!     at emitErrorCloseNT (node:internal/streams/destroy:128:3)
npm ERR!     at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
npm ERR!  FetchError: request to https://registry.npmjs.org/react failed, reason: 
npm ERR!     at ClientRequest.<anonymous> (/usr/share/nodejs/minipass-fetch/lib/index.js:130:14)
npm ERR!     at ClientRequest.emit (node:events:524:28)
npm ERR!     at emitErrorEvent (node:_http_client:101:11)
npm ERR!     at TLSSocket.socketErrorListener (node:_http_client:504:5)
npm ERR!     at TLSSocket.emit (node:events:536:35)
npm ERR!     at emitErrorNT (node:internal/streams/destroy:169:8)
npm ERR!     at emitErrorCloseNT (node:internal/streams/destroy:128:3)
npm ERR!     at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
npm ERR!   code: 'ECONNREFUSED',
npm ERR!   errno: 'ECONNREFUSED',
npm ERR!   type: 'system',
npm ERR!   requiredBy: '.'
npm ERR! }
npm ERR! 
npm ERR! If you are behind a proxy, please make sure that the
npm ERR! 'proxy' config is set properly.  See: 'npm help config'

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/amnesia/.npm/_logs/X-debug-0.log

Hi @tornpm, welcome to the forum.

I’ve just tried that URL (https://registry.npmjs.org/react) in Tor Browser on Linux with a variety of exit nodes and it renders the JSON just fine. NPM are not blanket-blocking tor exit node IP’s.

If you can share code for a minimum reproducible example that illustrates the problem perhaps a Tails user here can help figure out what the problem is.

Sorry to say this I would avoid NPM altogether I’m sorry to much security risks IMO

I’m not saying you are wrong or even defending NPM but you do not offer any facts to substantiate this claim. Where does this info come from and who is saying it? Give us a link or two that we may read and preferably someone or somewhere with credentials and not a Tik Tok link.