Which versions of yq-go are malicious?

Every published version of yq-go on npm is considered malicious. Remove the package entirely.

How do I remediate yq-go if I installed it?

Remove yq-go from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed yq-go — how do I know if it already compromised me?

If yq-go 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.

How do I find yq-go across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for yq-go (all published versions).

Malicious package

yq-gonpm

Advisory published Dec 1, 2025Updated Dec 1, 2025

yq-go is a confirmed malicious npm package (MAL-2025-191532) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in yq-go (npm)

MAL-2025-191532

Immediate action

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

npm uninstall yq-go

What this malware does

The package yq-go was found to contain malicious code.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

7d5276b7426a78180800c09848c996c357433cc3cec323ca62f8c45b89b14bf7

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for yq-go (all published versions).
If you installed it — respond
Remove yq-go from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If yq-go 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. yq-go on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks yq-go-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database