Reference
Dark server room with red warning lights and code displays
HighCyber Attacks

Xygeni GitHub Action Compromised in Supply Chain Attack

Attackers compromised AppSec vendor Xygeni's GitHub Action through tag poisoning, operating a command-and-control implant for up to one week.

Emanuel DE ALMEIDA 11 Mar 2026, 21:22 2 min read 5 views 0 Comments

Last updated 12 Mar 2026, 01:57

Key Takeaways

Xygeni GitHub Action Targeted in Tag Poisoning Attack

Attackers successfully compromised the xygeni/xygeni-action GitHub repository belonging to application security vendor Xygeni. The breach involved tag poisoning, a technique where malicious actors manipulate version tags to distribute compromised code through what appears to be legitimate software updates.

The attack allowed threat actors to establish and maintain an active command-and-control implant within the compromised action. This C2 infrastructure remained operational for up to seven days before detection.

Supply Chain Impact on Development Workflows

The compromise directly affects organizations and developers who integrated Xygeni's GitHub Action into their CI/CD pipelines. Any workflows that pulled the poisoned tags during the active compromise period potentially executed malicious code within their development environments.

The attack represents a significant supply chain security incident, as GitHub Actions are commonly used across enterprise development workflows for automated security scanning and compliance checks.

Tag Poisoning Enables Persistent Access

The attackers leveraged tag poisoning to maintain persistence within the legitimate software distribution channel. This technique exploits the trust developers place in version tags, allowing malicious code to be distributed through what appears to be routine software updates.

The week-long operation of the C2 implant indicates the attackers had sustained access to execute commands and potentially exfiltrate data from affected development environments. Organizations using the compromised action should audit their CI/CD logs for the affected timeframe.

Frequently Asked Questions

What is tag poisoning in GitHub Actions?
Tag poisoning is an attack technique where malicious actors manipulate version tags in repositories to distribute compromised code through legitimate software update channels.
How long was the Xygeni GitHub Action compromised?
The attackers operated an active command-and-control implant within the compromised Xygeni GitHub Action for up to one week before detection.
Which organizations are affected by the Xygeni compromise?
Any organizations or developers who used Xygeni's xygeni/xygeni-action in their CI/CD pipelines during the compromise period are potentially affected by this supply chain attack.

About the Author

Emanuel DE ALMEIDA

Emanuel DE ALMEIDA

Senior IT Journalist & Cloud Architect

Microsoft MCSA-certified Cloud Architect | Fortinet-focused. I modernize cloud, hybrid & on-prem infrastructure for reliability, security, performance and cost control - sharing field-tested ops & troubleshooting.

Discussion

Share your thoughts and insights

You must be logged in to comment.

Loading comments...