CriticalGitHub Actions14 affected versions

codfish/semantic-release-action

codfish/semantic-release-action has 14 versions on the GitHub Actions marketplace flagged in 1 incident we track. Other versions of this package are not implicated - only the exact versions listed below were named by the source advisories.

Affected versions

Check what you actually have installed.

codfish/semantic-release-action@v5.0.0
codfish/semantic-release-action@v5
codfish/semantic-release-action@v4.0.1
codfish/semantic-release-action@v4.0.0
codfish/semantic-release-action@v4
codfish/semantic-release-action@v3.5.0
codfish/semantic-release-action@v3.4.0
codfish/semantic-release-action@v3.3.0
codfish/semantic-release-action@v3.2.0
codfish/semantic-release-action@v3.1.0
codfish/semantic-release-action@v3.0.0
codfish/semantic-release-action@v3
codfish/semantic-release-action@v2.2.1
codfish/semantic-release-action@v2

The incident that flagged it

Critical24 Jun 2026

codfish/semantic-release-action - 16 tags retargeted to Miasma imposter commit

On 2026-06-24 at 15:39:06 UTC an attacker force-pushed two imposter commits to codfish/semantic-release-action and repointed 16 tags - including the floating majors v2, v3, v4, v5 - to them. Any workflow pinned by tag pulls 781,580 bytes of obfuscated JavaScript that searches GitHub commit-search for the thebeautifulsnadsoftime Miasma dead-drop channel and eval()s any signed payload, exfiltrating GITHUB_TOKEN and NPM_TOKEN from release workflows.

Versions named here: v2, v2.2.1, v3, v3.0.0, v3.1.0, v3.2.0, v3.3.0, v3.4.0, v3.5.0, v4, v4.0.0, v4.0.1, v5, v5.0.0

What to do if you installed one of these

Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

1.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
2.Pin to a version not listed above, then reinstall from a clean lockfile.
3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
4.Read the incident write-up above - recommended actions differ per incident, and some have specific indicators of compromise worth grepping your logs for.

Check your whole project

codfish/semantic-release-action is one of many packages in these incidents, and it is usually pulled in as a transitive dependency rather than one you installed directly. We don't parse GitHub Actions manifests yet, but the incident write-ups list every affected package.

Browse the incident feed All flagged GitHub Actions packages

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Think this is wrong or incomplete? Tell us.