xygeni-action
Xygeni GitHub Action v5 tag poisoning compromise
Compromised Xygeni maintainer and GitHub App credentials were used to open malicious pull requests against xygeni/xygeni-action, but branch protections blocked the changes from merging. The attacker instead moved the mutable v5 tag to a malicious PR commit, so workflows pinned to xygeni/xygeni-action@v5 could execute a reverse-shell backdoor without any workflow-file change. Xygeni removed the poisoned tag, rotated credentials, removed the compromised app, and enabled tag protections and release immutability. The vendor reported no main-branch, SaaS, customer-data, or confirmed customer CI compromise.
- Date
- 2026-03-03 to 2026-03-10
- Category
- Commercial
- Target Surface
- Revision control
- Insertion Phase
- source
- Impact
- Remote code execution
- Cause
- Compromised Account/Credentials
What Was Affected
Package
xygeni-action
LanguageYAML/Shell
ComponentCI/CD plugin
Artifact typeGitHub Action
Domain typesource host
Domain
github.com
Repository
github.com/xygeni/xygeni-action
Compromised Versions
- xygeni/xygeni-action@v5
Incident Context
- Motive
- Credential Theft/Remote Access
- Transitive
- No
- User Impact
- 0
- Observed Duration
- 7 days
Evidence
Compromised Artifacts
- github.com/xygeni/xygeni-action/tree/4bf1d4e19ad81a3e8d4063755ae0f482dd3baf12
- github.com/xygeni/xygeni-action/pull/46
- github.com/xygeni/xygeni-action/pull/47
- github.com/xygeni/xygeni-action/pull/48
- github.com/xygeni/xygeni-action/issues/54
Current Artifacts and Analysis
Indicators and Changes
Commits
External References
Source Data
Source record: proprietary/xygeni-action/meta.yaml