[BUG] NPM 11.6.2 does not run on Ubuntu

[1dEraNCeSIv0]

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

NPM 11.6.2, as installed with Node 25.0.0 according to the official docs, does not run on ubuntu (tested 24.04, 25.10). Instead running any command results in the error message "node: error while loading shared libraries: libatomic.so.1: cannot open shared object file: No such file or directory".

Npm 11.6.1, as installed with node 24.10.0, works without issues.

Note that I'm unsure whether to file this with npm or nvm. If you feel this should be an issue with nvm instead let me know.

Expected Behavior

NPM successfully starts and executes commands on Ubuntu 25.10

Steps To Reproduce

If you have access to docker the following steps always reproduce the issue for me:

1. Start a container with ubuntu 25.10

docker run -it --rm ubuntu:25.10 /bin/bash

2. Install curl

apt-get update && apt-get -y install curl

3. Install nvm as suggested in the docs according to the nvm install instructions

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash

export NVM_DIR="$([ -z "${XDG_CONFIG_HOME-}" ] && printf %s "${HOME}/.nvm" || printf %s "${XDG_CONFIG_HOME}/nvm")"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"

4. Use nvm to install npm

nvm install 25.0.0

5. Run any npm command

npm --version

6. Npm fails with "node: error while loading shared libraries: libatomic.so.1: cannot open shared object file: No such file or directory"

Environment

• npm: 11.6.2
• Node.js: 25.0.0
• OS Name: Ubuntu 25.10 (or 24.04)
• System Model Name: VMware Virtual Platform
• npm config (Note: this only prints after manually installing libatomic1, prior to that it shows the same error as above)

; node bin location = /root/.nvm/versions/node/v25.0.0/bin/node
; node version = v25.0.0
; npm local prefix = /
; npm version = 11.6.2
; cwd = /
; HOME = /root
; Run `npm config ls -l` to show all defaults.

[Tejas242]

If I am not wrong, this appears to be a Node.js system dependency issue rather than an npm bug.