Which versions of @nstudio/web-angular are malicious?

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

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

@nstudio/web-angular 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-angular — how do I know if it already compromised me?

If @nstudio/web-angular 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-angular part of a known attack campaign?

Yes — @nstudio/web-angular is associated with the GHSA-pmrr-9qcr-gcmp 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-angular 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-angular (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-angular across your stack and pipelines.

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

Malicious package

@nstudio/web-angularnpm

@nstudio/web-angular is a confirmed malicious npm package (MAL-2025-47168) 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-angular (npm)

MAL-2025-47168

Immediate action

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

npm uninstall @nstudio/web-angular

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)

19e2b2f064a728f3b2e6564cef5f7c00fc9a166f8a2e97291041de79f3b572c2

7be8318f173e1d2a979a5fbd100d34e26fd51036f3ae4339a7210f1878f947ef

23c4ed4cb860a43bc6617a8381e96547eb5ccb72913d84f791bd679ecd72b446

a58141e0a669709f29e547dac500a926657b88c52b0c3b86c590fd38ad3d9ae9

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-angular (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-angular across your stack and pipelines.
If you installed it — respond
@nstudio/web-angular 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-angular 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-angular 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-angular 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-pmrr-9qcr-gcmp

References

Detect & block this

O3 blocks @nstudio/web-angular-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