<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: GitHub Actions Supply Chain Compromise - tj-actions in Threats</title>
    <link>https://community.isc2.org/t5/Threats/GitHub-Actions-Supply-Chain-Compromise-tj-actions/m-p/78083#M1548</link>
    <description>&lt;P&gt;Hi All&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A sophisticated cascading supply chain attack has compromised multiple GitHub Actions, exposing critical CI/CD secrets across tens of thousands of repositories. The attack, which originally targeted the widely used “tj-actions/changed-files” utility, is now believed to have originated from an earlier breach of the “reviewdog/action-setup@v1” GitHub Action, according to a report.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Source:&amp;nbsp; Cryptogram - Bruce Schneier&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;CISA confirmed the vulnerability has been patched in version 46.0.1.&lt;/P&gt;&lt;P&gt;Given that the utility is used by more than 23,000 GitHub repositories, the scale of potential impact has raised significant alarm throughout the developer community.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Caute_Cautim&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 21 Mar 2025 03:06:24 GMT</pubDate>
    <dc:creator>Caute_cautim</dc:creator>
    <dc:date>2025-03-21T03:06:24Z</dc:date>
    <item>
      <title>GitHub Actions Supply Chain Compromise - tj-actions</title>
      <link>https://community.isc2.org/t5/Threats/GitHub-Actions-Supply-Chain-Compromise-tj-actions/m-p/77926#M1539</link>
      <description>&lt;P&gt;&lt;SPAN&gt;tj-actions/changed-files, has been compromised with a payload that appears to attempt to dump secrets, impacting thousands of CI pipelines.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://www.stepsecurity.io/blog/harden-runner-detection-tj-actions-changed-files-action-is-compromised" target="_blank"&gt;https://www.stepsecurity.io/blog/harden-runner-detection-tj-actions-changed-files-action-is-compromised&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://www.upwind.io/feed/github-actions-supply-chain-compromise-tj-actions-changed-files-action" target="_blank"&gt;https://www.upwind.io/feed/github-actions-supply-chain-compromise-tj-actions-changed-files-action&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 15 Mar 2025 17:45:34 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Threats/GitHub-Actions-Supply-Chain-Compromise-tj-actions/m-p/77926#M1539</guid>
      <dc:creator>akkem</dc:creator>
      <dc:date>2025-03-15T17:45:34Z</dc:date>
    </item>
    <item>
      <title>Re: GitHub Actions Supply Chain Compromise - tj-actions</title>
      <link>https://community.isc2.org/t5/Threats/GitHub-Actions-Supply-Chain-Compromise-tj-actions/m-p/77972#M1542</link>
      <description>We always recommend using a checksum or digest before deploying anything to a system. If you have verified the SHA value during installation to ensure you're using the correct version of tj-actions, then you are not compromised. Otherwise, regardless of the tag, all versions are vulnerable, as tags can be modified to push the same vulnerable code.</description>
      <pubDate>Mon, 17 Mar 2025 23:50:03 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Threats/GitHub-Actions-Supply-Chain-Compromise-tj-actions/m-p/77972#M1542</guid>
      <dc:creator>akkem</dc:creator>
      <dc:date>2025-03-17T23:50:03Z</dc:date>
    </item>
    <item>
      <title>Re: GitHub Actions Supply Chain Compromise - tj-actions</title>
      <link>https://community.isc2.org/t5/Threats/GitHub-Actions-Supply-Chain-Compromise-tj-actions/m-p/77986#M1546</link>
      <description>&lt;P&gt;This is very informative. Thank you for sharing your time and experience with us in this forum&amp;nbsp;&lt;a href="https://community.isc2.org/t5/user/viewprofilepage/user-id/111970903"&gt;@akkem&lt;/a&gt;.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Mar 2025 12:04:19 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Threats/GitHub-Actions-Supply-Chain-Compromise-tj-actions/m-p/77986#M1546</guid>
      <dc:creator>Kyaw_Myo_Oo</dc:creator>
      <dc:date>2025-03-18T12:04:19Z</dc:date>
    </item>
    <item>
      <title>Re: GitHub Actions Supply Chain Compromise - tj-actions</title>
      <link>https://community.isc2.org/t5/Threats/GitHub-Actions-Supply-Chain-Compromise-tj-actions/m-p/78083#M1548</link>
      <description>&lt;P&gt;Hi All&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A sophisticated cascading supply chain attack has compromised multiple GitHub Actions, exposing critical CI/CD secrets across tens of thousands of repositories. The attack, which originally targeted the widely used “tj-actions/changed-files” utility, is now believed to have originated from an earlier breach of the “reviewdog/action-setup@v1” GitHub Action, according to a report.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Source:&amp;nbsp; Cryptogram - Bruce Schneier&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;CISA confirmed the vulnerability has been patched in version 46.0.1.&lt;/P&gt;&lt;P&gt;Given that the utility is used by more than 23,000 GitHub repositories, the scale of potential impact has raised significant alarm throughout the developer community.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Caute_Cautim&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Mar 2025 03:06:24 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Threats/GitHub-Actions-Supply-Chain-Compromise-tj-actions/m-p/78083#M1548</guid>
      <dc:creator>Caute_cautim</dc:creator>
      <dc:date>2025-03-21T03:06:24Z</dc:date>
    </item>
    <item>
      <title>Re: GitHub Actions Supply Chain Compromise - tj-actions</title>
      <link>https://community.isc2.org/t5/Threats/GitHub-Actions-Supply-Chain-Compromise-tj-actions/m-p/78179#M1552</link>
      <description>Supply chain and OAuth attacks are on the rise in GitHub, threat campaign targeting over 8,000 repositories with the goal of luring developers into granting full repository access. Mitiga’s researchers explain an active GitHub compromise and large-scale phishing campaign, along with providing recommendations for threat hunting and mitigation.&lt;BR /&gt;&lt;A href="https://www.mitiga.io/blog/uncovering-hidden-threats-hunting-non-human-identities-in-github?utm_source=Marketo&amp;amp;utm_medium=Email&amp;amp;utm_campaign=MonthlyNewsletter&amp;amp;mkt_tok=NDIyLURKUC0xNjEAAAGZZv92weMEvYsFdrKojktdAFzWR24xakr8gAQ4JFXwD4D1oaHd4FeyKsRbNbGfYGuoX_FY9pI0sro_xCvPNeT1ye-KSXEvisvdHk8s1SdD" target="_blank"&gt;https://www.mitiga.io/blog/uncovering-hidden-threats-hunting-non-human-identities-in-github?utm_source=Marketo&amp;amp;utm_medium=Email&amp;amp;utm_campaign=MonthlyNewsletter&amp;amp;mkt_tok=NDIyLURKUC0xNjEAAAGZZv92weMEvYsFdrKojktdAFzWR24xakr8gAQ4JFXwD4D1oaHd4FeyKsRbNbGfYGuoX_FY9pI0sro_xCvPNeT1ye-KSXEvisvdHk8s1SdD&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 24 Mar 2025 12:42:31 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Threats/GitHub-Actions-Supply-Chain-Compromise-tj-actions/m-p/78179#M1552</guid>
      <dc:creator>akkem</dc:creator>
      <dc:date>2025-03-24T12:42:31Z</dc:date>
    </item>
  </channel>
</rss>

