[BUG] npm exec requires elevation for some packages

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

Executing any npm package in an unelevated shell will output this (the text is even like this in PowerShell):

'"node"' is not recognized as an internal or external command,
operable program or batch file.

It works as expected when the shell is elevated.

Expected Behavior

ESLint was meant to be executed and see what issues were in the JavaScript file.

Steps To Reproduce

1. Create a script.js file in a directory. Make sure you have ESLint installed.
2. Open the directory with the script.js file in a normal shell (i.e. without elevation).
3. Run npm exec eslint script.js.

Environment

• npm: 8.19.2
• Node.js: v18.9.0
• OS Name: Windows 11 Version 22H2 Build 22621.521
• System Model Name: Acer Nitro 5
• npm config:

; "builtin" config from C:\Users\Keyacom\AppData\Roaming\npm\node_modules\npm\npmrc

prefix = "C:\\Users\\Keyacom\\AppData\\Roaming\\npm"

; node bin location = C:\Program Files\nodejs\node.exe
; node version = v18.9.0
; npm local prefix = C:\Users\Keyacom\documents\github\pages-from-school\psi\grade2\reklama-anim
; npm version = 8.19.2
; cwd = C:\Users\Keyacom\documents\github\pages-from-school\psi\grade2\reklama-anim
; HOME = C:\Users\Keyacom

NOTE: Originally filed as eslint/eslint#16338. I've tested this with Prettier, and the same issue happened.

Reproduce the problem on Windows 11 by running npm exec eslint script.js from an unelevated shell, then compare it with the elevated-shell behavior. Trace the npm exec path involved in launching ESLint and verify that the command runs successfully without elevation, including the reported PowerShell error case.