Ethical Hacking News
A leaked GitHub token and the subsequent hijacking of a release pipeline have sent shockwaves throughout the cybersecurity community. The incident highlights the growing threat of supply chain attacks and the need for increased vigilance in protecting sensitive information. Learn more about the incident and its implications in our latest article.
A leaked GitHub token and hijacked release pipeline have sent shockwaves through the cybersecurity community. A mistake allowed an attacker to access a repository and extract a GitHub CLI OAuth token with owner-level access. The attacker was able to possess owner-level access, perform credential exfiltration, and execute malicious workflows. The malicious workflows captured sensitive information, including tokens associated with multiple services. The attack exploited a vulnerability in LiteLLM version 1.107.0 and was carried out by an unknown attacker. The incident highlights the importance of robust security controls, regular monitoring, and token revocation.
The recent revelation of a leaked GitHub token and the subsequent hijacking of a release pipeline has sent shockwaves throughout the cybersecurity community. The incident, which occurred on October 21, 2026, highlights the growing threat of supply chain attacks and the need for increased vigilance in protecting sensitive information.
According to a report by LiteLLM, a popular Python package, an agent platform master key was accidentally published to a public GitHub repository in late May 2026. This mistake allowed an attacker to gain access to the repository and extract a GitHub CLI OAuth token, which was associated with the GitHub organization owner's account.
The token, per the developers of the open-source large language model (LLM) gateway, was "not scoped down" and gave the attacker owner-level access to all repositories across the organization. The attacker was able to possess this level of access, perform additional credential exfiltration, and execute malicious workflows designed to acquire GitHub CLI OAuth tokens associated with two engineers with maintainer privileges.
The malicious workflows, designed to harvest GitHub tokens and API keys for the organization's Linear workspace, LiteLLM deployment, and Together AI, also captured sensitive information such as system information, SSH files, Git and GitLab credentials, environment variables, and tokens associated with npm, PyPI, pip, Yarn, Maven, Gradle, Composer, RubyGems, and Cargo.
The attack, which was carried out by an unknown attacker, was able to exploit a vulnerability in the LiteLLM version 1.107.0 package. The package, which was published to PyPI on October 21, 2026, contained two execution paths: a credential harvesting module that targeted authentication material across developer tools, AI applications, cloud environments, and web browsers, and a Unix-oriented backdoor that was launched as a background process to fetch and execute arbitrary code supplied by the attacker every one hour.
The attack was able to collect system information, SSH files, Git and GitLab credentials, environment variables, and tokens associated with various services, including Anthropic, OpenAI, AWS Bedrock, Tavily, and GitGuardian's secret-scanning tenant. The data was then compressed and sent to "litellm[.]dev/healthcheck" using an HTTP POST request.
The incident highlights the importance of maintaining robust security controls and monitoring for potential vulnerabilities. It also underscores the need for developers to regularly review and update their dependencies to ensure they are using the latest and most secure versions.
In response to the incident, LiteLLM has stated that it is working to revoke each and every token associated with every internal system and vendor platform. The company has also emphasized the importance of token revocation and the need for organizations to regularly review and update their access controls.
The incident serves as a stark reminder of the growing threat of supply chain attacks and the need for increased vigilance in protecting sensitive information. It highlights the importance of robust security controls, regular monitoring, and token revocation in preventing similar incidents in the future.
Related Information:
https://www.ethicalhackingnews.com/articles/EXPOSED-The-Devastating-Consequences-of-a-Leaked-GitHub-Token-and-the-Rise-of-Supply-Chain-Attacks-ehn.shtml
https://thehackernews.com/2026/10/leaked-litellm-master-key-let-attackers.html
Published: Sat Oct 24 08:21:13 2026 by llama3.2 3B Q4_K_M
