Which versions of dotnet-template are malicious?

The following npm versions of dotnet-template are flagged malicious: 0.0.3, 0.0.4. Treat any of these as compromised.

How do I remediate dotnet-template if I installed it?

dotnet-template 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 dotnet-template — how do I know if it already compromised me?

If dotnet-template was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is dotnet-template part of a known attack campaign?

Yes — dotnet-template is associated with the GHSA-x7qc-cwwv-rj89 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 dotnet-template across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dotnet-template (2 malicious versions).

Malicious package

dotnet-templatenpm

Advisory published Nov 24, 2025Updated Nov 26, 2025

dotnet-template is a confirmed malicious npm package (MAL-2025-190770) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.3, 0.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dotnet-template (npm)

MAL-2025-190770

Immediate action

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

npm uninstall dotnet-template

What this malware does

The package dotnet-template was found to contain malicious code.

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 Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

2 flagged

0.0.30.0.4

Indicators of compromise (SHA-256)

01d263352d7df50818b3c0bfb8c2c2b4c30e78dcf1feadeb4b808c2636b9c6a6

09b8736e74e763b930253cc92ff8ee4e0b0c323b712ea201cd40c8590f618b72

74d3fb73b3f121ff577bedfe3e3090fa09111d786eba803dd7550f81f4eb1d3b

0acc1a0892fdffc0796372a48d4bd02e88c6120261ee67f21cb65d370b1ad809

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for dotnet-template (2 malicious versions).
If you installed it — respond
dotnet-template 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 dotnet-template was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. dotnet-template on npm has been identified as a malicious package (versions 0.0.3, 0.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-x7qc-cwwv-rj89

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dotnet-template-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