Which versions of @nstudio/web are malicious?

The following npm versions of @nstudio/web are flagged malicious: 20.0.4. Treat any of these as compromised.

How do I remediate @nstudio/web if I installed it?

@nstudio/web is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @nstudio/web — how do I know if it already compromised me?

If @nstudio/web was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @nstudio/web part of a known attack campaign?

Yes — @nstudio/web is associated with the GHSA-r6x6-85h3-39v6 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @nstudio/web across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @nstudio/web (version 20.0.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @nstudio/web across your stack and pipelines.

Part of a larger attack: @nstudio published 9 malicious packages. See the full campaign →

Malicious package

@nstudio/webnpm

@nstudio/web is a confirmed malicious npm package (MAL-2025-47167) that steals credentials and exfiltrates sensitive data (malicious version 20.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @nstudio/web (npm)

MAL-2025-47167

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @nstudio/web

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This package was compromised by the Shai-Hulud NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub before propogating itself to NPM packages the user owns.

Malicious versions

1 flagged

20.0.4

Indicators of compromise (SHA-256)

2c10ca009d851af8a5cd991038674696dcba73033bd87678ae2187dde082e8e5

8aa60eb7f95bf7a14bc6bf948b78a2f577a4f67775d0982e87491a3e4ebaec8f

2b1eb1a964b26e60efddcc786091d6563638c73c678ef54adbfea166a0aef929

f94e4290eff0ecb6b6c664c70e928d0e5614271d3c459091a13832c9ada87f21

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @nstudio/web (version 20.0.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @nstudio/web across your stack and pipelines.
If you installed it — respond
@nstudio/web is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @nstudio/web was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @nstudio/web before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @nstudio/web on npm has been identified as a malicious package (version 20.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-r6x6-85h3-39v6

References

Detect & block this

O3 blocks @nstudio/web-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database