From b31f8f2a8d45a2cdc45bc8def48fdcd9e5213572 Mon Sep 17 00:00:00 2001 From: ankithbharadwaj Date: Mon, 13 Jul 2026 19:47:50 +0530 Subject: [PATCH] testubg --- docs/Vulnerabilities/TamperingDuringBuild.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Vulnerabilities/TamperingDuringBuild.md b/docs/Vulnerabilities/TamperingDuringBuild.md index 1876b6c80..054d9a2f9 100644 --- a/docs/Vulnerabilities/TamperingDuringBuild.md +++ b/docs/Vulnerabilities/TamperingDuringBuild.md @@ -5,7 +5,7 @@ GitHub Actions workflows can be poisoned, potentially leading to the tampering o 1. **Direct Workflow Alteration:** An attacker can directly modify the workflow, introducing code that tampers source code or artifacts on disk during build. 2. **Utilizing Malicious or Vulnerable Dependencies:** An attacker might exploit a GitHub Action or any other dependency incorporated in the workflow that has been tampered with or is inherently vulnerable. 3. **Code Execution During Workflow Run:** A scenario can occur where code with harmful intent gets executed during a workflow run. This could be instigated through a seemingly innocuous component such as a test case. -4. **Build Server Compromise:** An attacker might attempt to breach the security of the build server on which the GitHub Actions workflow runs. +4. **Build Server Compromise:** An attacker might attempt to breach the security of the build server on which the GitHub Actions workflow runs. tihs is a rest ## Summary of past incidents