GitHub's popular actions-cool/issues-helper workflow fell victim to a supply chain attack that redirected repository tags to malicious commits. Threat actors compromised the repository and reconfigured every existing tag to point to impostor commits absent from the action's legitimate commit history.

The attack weaponized the workflow to execute malicious code designed to harvest CI/CD credentials and exfiltrate them to attacker-controlled infrastructure. Organizations using actions-cool/issues-helper in their GitHub Actions pipelines faced direct exposure to credential theft.

The compromise exploits a critical weakness in how developers reference GitHub Actions. Many teams pin workflows to specific version tags rather than commit hashes. When threat actors redirect those tags, they force automated deployments to pull and execute malicious code without developer awareness. This technique bypasses standard code review processes because the attack occurs at the repository level, not in individual workflows.

The impact extends beyond the immediate repository. Any organization running this action automatically received the poisoned version during their next CI/CD pipeline execution. GitHub Actions workflows typically run with elevated privileges and access to secrets like deployment tokens, API keys, and authentication credentials. Stolen credentials enable attackers to pivot into target environments, deploy backdoors, or access downstream systems.

This attack underscores a persistent supply chain vulnerability. GitHub Actions repositories with write access concentrate significant trust. A single compromised maintainer account or weak credentials on a popular action creates blast radius effects across thousands of dependent projects.

The security community's response included immediate disclosure and user notification. Security teams should audit their GitHub Actions workflow definitions to identify which versions of actions-cool/issues-helper they're running. Organizations should verify whether any suspicious credential usage occurred around the compromise timeframe.

Mitigation requires pinning workflows to commit SHAs rather than tags whenever possible. This practice prevents tag redirection attacks by forcing explicit commit references. Security scanning tools should flag any GitHub Actions dependencies and