Executive Summary
In March 2026, a threat actor utilized AI-assisted automation to execute over 450 exploit attempts against open-source repositories on GitHub. The campaign, identified as 'prt-scan,' specifically targeted repositories misconfigured with the 'pull_request_target' workflow trigger. While less than 10% of these attempts were successful, the attacker managed to compromise at least two NPM packages, leading to the exposure of ephemeral GitHub credentials. This incident underscores the growing trend of AI-enhanced supply chain attacks, where adversaries leverage automation to scale their operations and exploit common misconfigurations. Organizations are urged to review and secure their CI/CD pipelines to mitigate such risks.
Why This Matters Now
The 'prt-scan' campaign highlights the increasing use of AI in automating large-scale supply chain attacks, making it imperative for organizations to proactively secure their development environments against such evolving threats.
Attack Path Analysis
The attacker utilized AI-assisted automation to scan for GitHub repositories misconfigured with the 'pull_request_target' workflow trigger, enabling them to submit malicious pull requests. Upon successful execution, these pull requests allowed the attacker to access repository secrets and credentials, potentially escalating privileges within the compromised environment. The attacker then attempted to move laterally by leveraging the obtained credentials to access other parts of the victim's infrastructure. Command and control were established through the compromised repositories, enabling the attacker to issue commands and exfiltrate data. Sensitive data, including API keys and environment variables, were exfiltrated from the compromised repositories. The impact included unauthorized access to repositories, potential data breaches, and the risk of further exploitation through the compromised credentials.
Kill Chain Progression
Initial Compromise
Description
The attacker utilized AI-assisted automation to scan for GitHub repositories misconfigured with the 'pull_request_target' workflow trigger, enabling them to submit malicious pull requests.
Related CVEs
CVE-2026-27941
CVSS 9.9OpenLIT versions prior to 1.37.1 contain a broken access control vulnerability due to the use of the pull_request_target event in GitHub Actions workflows, allowing attackers to execute untrusted code with base repository privileges.
Affected Products:
OpenLIT OpenLIT – < 1.37.1
Exploit Status:
proof of conceptCVE-2026-22869
CVSS 9.8Eigent's CI workflow allows arbitrary code execution from fork pull requests with repository write permissions due to the use of the pull_request_target trigger combined with checkout of untrusted PR code.
Affected Products:
Eigent Eigent – unspecified
Exploit Status:
proof of conceptCVE-2026-24480
CVSS 8.7QGIS GitHub Actions workflow is vulnerable to remote code execution due to insecure use of the pull_request_target trigger, allowing attackers to execute arbitrary commands with elevated privileges.
Affected Products:
QGIS QGIS – unspecified
Exploit Status:
proof of conceptCVE-2026-1699
CVSS 8.8Eclipse Theia Website's GitHub Actions workflow uses the pull_request_target trigger while checking out and executing untrusted pull request code, allowing any GitHub user to execute arbitrary code in the repository's CI environment with access to repository secrets.
Affected Products:
Eclipse Theia Website – unspecified
Exploit Status:
proof of concept
MITRE ATT&CK® Techniques
Supply Chain Compromise: Compromise Software Dependencies and Development Tools
Valid Accounts
Unsecured Credentials: Credentials in Files
Command and Scripting Interpreter: PowerShell
Archive Collected Data: Archive via Utility
Exfiltration Over C2 Channel
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Ensure software security for public-facing web applications
Control ID: 6.3.2
NYDFS 23 NYCRR 500 – Cybersecurity Policy
Control ID: 500.03
DORA – ICT Risk Management Framework
Control ID: Article 5
CISA ZTMM 2.0 – Identity and Access Management
Control ID: 3.1
NIS2 Directive – Cybersecurity Risk Management Measures
Control ID: Article 21
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Computer Software/Engineering
GitHub supply chain attacks directly compromise software repositories, exposing source code, credentials, and development workflows to AI-assisted automated exploitation campaigns.
Information Technology/IT
IT infrastructure management relies heavily on GitHub repositories for automation and configuration, making organizations vulnerable to credential theft and malicious code injection.
Financial Services
Financial institutions using open-source components face regulatory compliance violations and data exposure risks from compromised NPM packages and stolen API keys.
Health Care / Life Sciences
Healthcare software development using GitHub workflows risks HIPAA violations through exposed credentials and potential compromise of patient data processing applications.
Sources
- AI-Assisted Supply Chain Attack Targets GitHubhttps://www.darkreading.com/application-security/ai-assisted-supply-chain-attack-targets-githubVerified
- CVE-2026-27941 - OpenLIT - Broken Access Control | LeakyCredshttps://www.leakycreds.com/vulnerability/CVE-2026-27941Verified
- CVE-2026-22869 - Eigent Allows Arbitrary Code Execution via pull_request_target CI Workflowhttps://cvefeed.io/vuln/detail/CVE-2026-22869Verified
- CVE-2026-24480: QGIS GitHub Actions RCE Vulnerabilityhttps://www.sentinelone.com/vulnerability-database/cve-2026-24480/Verified
- CVE-2026-1699: Eclipse Theia Website RCE Vulnerabilityhttps://www.sentinelone.com/vulnerability-database/cve-2026-1699/Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Aviatrix Zero Trust CNSF is pertinent to this incident as it could likely limit the attacker's ability to exploit misconfigured GitHub repositories, restrict lateral movement within the infrastructure, and control unauthorized data exfiltration.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: Implementing Aviatrix CNSF would likely limit the attacker's ability to exploit misconfigured GitHub repositories by enforcing strict access controls and monitoring repository configurations.
Control: Zero Trust Segmentation
Mitigation: Zero Trust Segmentation would likely limit the attacker's ability to escalate privileges by enforcing strict identity-based access controls and segmenting sensitive resources.
Control: East-West Traffic Security
Mitigation: East-West Traffic Security would likely limit the attacker's lateral movement by monitoring and controlling internal traffic flows between workloads.
Control: Multicloud Visibility & Control
Mitigation: Multicloud Visibility & Control would likely limit the attacker's ability to establish command and control channels by providing comprehensive monitoring and management across cloud environments.
Control: Egress Security & Policy Enforcement
Mitigation: Egress Security & Policy Enforcement would likely limit the attacker's ability to exfiltrate sensitive data by controlling and monitoring outbound traffic.
Implementing Aviatrix Zero Trust CNSF would likely reduce the overall impact by limiting unauthorized access, constraining data breaches, and reducing the risk of further exploitation through compromised credentials.
Impact at a Glance
Affected Business Functions
- Software Development
- Continuous Integration/Continuous Deployment (CI/CD)
Estimated downtime: 3 days
Estimated loss: $50,000
Potential exposure of repository secrets, including API keys and credentials.
Recommended Actions
Key Takeaways & Next Steps
- • Implement Zero Trust Segmentation to enforce least privilege access and prevent unauthorized lateral movement within the network.
- • Utilize Egress Security & Policy Enforcement to monitor and control outbound traffic, reducing the risk of data exfiltration.
- • Deploy Threat Detection & Anomaly Response systems to identify and respond to unusual activities indicative of compromise.
- • Ensure Multicloud Visibility & Control to maintain oversight across all cloud environments and detect potential threats.
- • Regularly review and update security configurations, such as GitHub workflow triggers, to prevent exploitation of misconfigurations.



