CyberHappenings logo
☰
🏠 Home 📂 Browse ℹ️ About

Track cybersecurity events as they unfold. Sourced timelines, daily updates. Fast, privacy‑respecting. No ads, no tracking.

Security Risks in GitHub-hosted Code Across the Software Development Lifecycle

First reported
Last updated
📰 1 unique sources, 1 articles

Summary

Hide ▲

GitHub-hosted code introduces multiple risk vectors throughout the software development lifecycle (SDLC). These vectors create blind spots that attackers exploit, as seen in incidents like the tj-actions GitHub Action and XZ Utils compromises. Organizations often overlook these risks, focusing instead on scanning packaged dependencies from npm or PyPI. The risks span dependency management, container builds, Kubernetes deployments, configuration management, CI/CD automation, code organization, infrastructure provisioning, build tools, developer workflows, and cross-repository triggers. These vulnerabilities can lead to code execution with application privileges, environment variable exfiltration, and other malicious activities. To mitigate these risks, organizations must inventory GitHub references, standardize on pinned immutable references, implement integrity verification, and develop secure internal alternatives for common external dependencies.

Timeline

  1. 19.08.2025 17:00 📰 1 articles · ⏱ 28d ago

    Multiple GitHub-hosted Code Risk Vectors Identified Across the Software Development Lifecycle

    Research by OX Security identified ten major risk vectors in GitHub-hosted code throughout the software development lifecycle. These vectors include dependency management, container builds, Kubernetes deployments, configuration management, CI/CD automation, code organization, infrastructure provisioning, build tools, developer workflows, and cross-repository triggers. Each vector presents unique attack surfaces and real-world impacts, such as non-deterministic builds, environment variable exfiltration, and malicious code execution. Organizations must inventory GitHub references, standardize on pinned immutable references, implement integrity verification, and develop secure internal alternatives to mitigate these risks.

    Show sources
    Open in new tab

Information Snippets

  • Package managers like npm, pip, Maven, and Go modules can pull dependencies directly from GitHub repositories, leading to non-deterministic builds and repository hijacking risks.

    First reported: 19.08.2025 17:00
    📰 1 source, 1 article
    Show sources

  • Dockerfiles often use git clone or ADD/COPY with GitHub URLs to fetch source code, build tools, or setup scripts during image building, potentially reusing outdated or compromised code.

    First reported: 19.08.2025 17:00
    📰 1 source, 1 article
    Show sources

  • Helm charts or init containers in Kubernetes manifests can fetch configurations and scripts from GitHub, deploying malicious resources with cluster permissions.

    First reported: 19.08.2025 17:00
    📰 1 source, 1 article
    Show sources

  • Configuration management tools like Ansible, SaltStack, Logstash, and Grafana pull configurations or components directly from GitHub, executing with administrative privileges across infrastructure.

    First reported: 19.08.2025 17:00
    📰 1 source, 1 article
    Show sources

  • GitHub Actions leverage third-party actions or perform direct git clone operations within workflow execution, often with access to repository secrets and deployment credentials.

    First reported: 19.08.2025 17:00
    📰 1 source, 1 article
    Show sources

  • Git submodules and subtrees embed external repositories within projects, creating complex dependency trees that can introduce malicious code during updates.

    First reported: 19.08.2025 17:00
    📰 1 source, 1 article
    Show sources

  • Infrastructure-as-code modules sourced directly from GitHub automate cloud resource provisioning, potentially provisioning resources under attacker control or embedding malicious startup scripts in VMs.

    First reported: 19.08.2025 17:00
    📰 1 source, 1 article
    Show sources

  • Build tools like Gradle and applications like Redis load plugins directly from GitHub, extending functionality beyond core features and introducing risks of environment variable exfiltration.

    First reported: 19.08.2025 17:00
    📰 1 source, 1 article
    Show sources

  • Git hooks and package manager lifecycle scripts run automatically early in development workflows, executing with minimal user interaction and potentially stealing credentials or installing malware.

    First reported: 19.08.2025 17:00
    📰 1 source, 1 article
    Show sources

  • Repository_dispatch events allow one repository to trigger workflows in another via API calls, potentially forging repository_dispatch events if a token is obtained.

    First reported: 19.08.2025 17:00
    📰 1 source, 1 article
    Show sources

Similar Happenings

Supply Chain Attack Targeting npm Registry Compromises 40 Packages

A supply chain attack targeting the npm registry has compromised over 187 packages maintained by multiple developers. The attack uses a malicious script (bundle.js) to steal credentials from developer machines. The compromised packages include various npm modules used in different projects. The attack is capable of targeting both Windows and Linux systems. The malicious script scans for secrets using TruffleHog's credential scanner and transmits them to an external server controlled by the attackers. Developers are advised to audit their environments and rotate credentials if the affected packages are present.

Open in new tab

Cursor AI editor autoruns malicious code in repositories

A flaw in the Cursor AI code editor allows malicious repositories to execute arbitrary code automatically when opened. This vulnerability can lead to malware installation, environment hijacking, and credential theft. Cursor, an AI-powered IDE based on Visual Studio Code, disables the Workspace Trust feature by default, allowing this behavior. The flaw affects one million users who generate over a billion lines of code daily. Cursor developers have decided not to fix the issue, citing the need to maintain AI and other features. The vulnerability is part of a broader trend of prompt injections and jailbreaks affecting AI-powered coding and reasoning agents, which can embed malicious instructions to perform harmful actions or leak data.

Open in new tab

Microsoft September 2025 Patch Tuesday fixes 81 vulnerabilities, including two zero-days

Microsoft released updates for 80 vulnerabilities on September 2025 Patch Tuesday. None of these vulnerabilities were zero-days. The updates address eight critical flaws, including five remote code execution vulnerabilities, one information disclosure, and two elevation of privilege vulnerabilities. The vulnerabilities span various categories: 38 elevation of privilege, 2 security feature bypass, 22 remote code execution, 14 information disclosure, 3 denial of service, and 1 spoofing. One zero-day vulnerability was fixed in Windows SMB Server. The updates also include hardening features for SMB Server to mitigate relay attacks, with recommendations for administrators to enable auditing. The patch includes 38 elevation of privilege vulnerabilities, the highest number among all categories. CVE-2025-54918 is an EoP vulnerability in Windows NT LAN Manager (NTLM) marked as critical. CVE-2025-54111 and CVE-2025-54913 are EoP flaws in Windows UI XAML, allowing privilege escalation via phished credentials or malicious Microsoft Store apps. CVE-2025-55232 is an RCE vulnerability in the Microsoft High Performance Compute (HPC) Pack with a CVSS score of 9.8. CVE-2025-54916 is an RCE vulnerability in Windows NTFS that can be triggered by authenticated users. Microsoft's patch update includes recommendations for preparing for the end-of-life of Windows 10 and mandatory multifactor authentication (MFA) for Azure in October 2025.

Open in new tab

Critical SAP NetWeaver vulnerabilities patched, including remote code execution flaw

SAP has fixed 21 vulnerabilities, including three critical flaws in its NetWeaver software. The most severe, CVE-2025-42944, is an insecure deserialization flaw allowing unauthenticated remote code execution. The second critical flaw, CVE-2025-42922, enables arbitrary file uploads by authenticated users. The third, CVE-2025-42958, allows unauthorized access to sensitive data and administrative functions. The vulnerabilities affect various SAP products, including ERP, CRM, SRM, and SCM, which are widely used in large enterprise networks. The flaws could lead to full system compromise and unauthorized data manipulation. SAP products are frequently targeted by threat actors due to their handling of mission-critical data. A high-severity missing input validation bug in SAP S/4HANA (CVE-2025-42916) could allow an attacker with high privilege access to delete the content of arbitrary database tables. A critical security defect in SAP S/4HANA (CVE-2025-42957) has come under active exploitation in the wild.

Open in new tab

Supply Chain Attack on npm Packages with Billions of Weekly Downloads

A supply chain attack compromised multiple npm packages with over 2.6 billion weekly downloads. Attackers injected malicious code into these packages after hijacking a maintainer's account via phishing. The malware targets web-based cryptocurrency transactions, redirecting them to attacker-controlled wallets. The attack was detected and mitigated by the NPM team, who removed the malicious versions within two hours. The phishing campaign targeted multiple maintainers, using a fake domain to trick them into updating their 2FA credentials. The malicious code operates by hooking into JavaScript functions and wallet APIs, intercepting and altering cryptocurrency transactions. The attack impacts users who installed the compromised packages during a specific time window and have vulnerable dependencies. The attack targeted Josh Junon, also known as Qix, who received a phishing email mimicking npm. The phishing email prompted the maintainer to enter their username, password, and 2FA token, which were stolen via an adversary-in-the-middle (AitM) attack. The attack affected 20 packages, including ansi-regex, chalk, debug, and others, with over 2 billion weekly downloads. The malware intercepts cryptocurrency transaction requests by computing the Levenshtein distance to swap the destination wallet address. The payload hooks into window.fetch, XMLHttpRequest, and window.ethereum.request, along with other wallet provider APIs. The attack also compromised another maintainer, duckdb_admin, to distribute the same wallet-drainer malware. The affected packages from the second maintainer include @coveops/abi, @duckdb/duckdb-wasm, and prebid, among others. The attack impacted roughly 10% of all cloud environments. The attackers diverted five cents worth of ETH and $20 worth of a virtually unknown memecoin. The attacker’s wallet addresses holding significant amounts have been flagged, limiting their ability to convert or use the funds.

Open in new tab