Which versions of @ctrl/golang-template are malicious?

The following npm versions of @ctrl/golang-template are flagged malicious: 1.4.2, 1.4.3. Treat any of these as compromised.

How do I remediate @ctrl/golang-template if I installed it?

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

If @ctrl/golang-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 @ctrl/golang-template part of a known attack campaign?

Yes — @ctrl/golang-template is associated with the GHSA-3xq6-jchq-ph3r 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 @ctrl/golang-template across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @ctrl/golang-template (2 malicious versions).

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

Malicious package

@ctrl/golang-templatenpm

Advisory published Sep 15, 2025Updated Sep 17, 2025

@ctrl/golang-template is a confirmed malicious npm package (MAL-2025-47132) that steals credentials and exfiltrates sensitive data (malicious versions 1.4.2, 1.4.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ctrl/golang-template (npm)

MAL-2025-47132

Immediate action

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

npm uninstall @ctrl/golang-template

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

2 flagged

1.4.21.4.3

Indicators of compromise (SHA-256)

d5ecdb39263cebdde95cdf053ac5e3bbb38aea40824853c2004d1ada8254e138

9d6092529af759b409d0a38be10b63c40c90a216dc37873d178c457326de597e

6e134ba497c6e5928159e1ffbb1c988b28cdd91be99d7bfe280b623012fc92c4

7b3a3c588763d1632656579ecf57dcc539d0178a7198c11f2d7015e7eccb0b55

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @ctrl/golang-template (2 malicious versions).
If you installed it — respond
@ctrl/golang-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 @ctrl/golang-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. @ctrl/golang-template on npm has been identified as a malicious package (versions 1.4.2, 1.4.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-3xq6-jchq-ph3r

References

Detect & block this

O3 blocks @ctrl/golang-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