<?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 Up-to-date detections for TeamPCP malware used in Trivy and Checkmarx compromises available? in Cortex XDR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/up-to-date-detections-for-teampcp-malware-used-in-trivy-and/m-p/1250823#M9215</link>
    <description>&lt;P&gt;Hi, we're currently using the data collected via XDR and other sensors to hunt for IOCs of the recently observed attacks against aquasecurity Trivy Github actions, as well as Checkmarx KICS. This, obviously, focuses mainly on network-based IOCs like C2 domain and IPs, as well as file hashes and version strings in filenames.&lt;BR /&gt;However, the attackers could easily change their malicious scripts to have a new hash, or point it to another domain and IP for C2. I'm thus evaluating what other options we'd have to scan for suspicious behaviour, particularly the way the malicious script scans for credentials and exfiltrates the collected information.&lt;BR /&gt;How can we get more information if PaloAlto is already working on such (BIOC) detection rules, and when they will be available?&lt;/P&gt;</description>
    <pubDate>Tue, 24 Mar 2026 09:51:51 GMT</pubDate>
    <dc:creator>MarekKreul</dc:creator>
    <dc:date>2026-03-24T09:51:51Z</dc:date>
    <item>
      <title>Up-to-date detections for TeamPCP malware used in Trivy and Checkmarx compromises available?</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/up-to-date-detections-for-teampcp-malware-used-in-trivy-and/m-p/1250823#M9215</link>
      <description>&lt;P&gt;Hi, we're currently using the data collected via XDR and other sensors to hunt for IOCs of the recently observed attacks against aquasecurity Trivy Github actions, as well as Checkmarx KICS. This, obviously, focuses mainly on network-based IOCs like C2 domain and IPs, as well as file hashes and version strings in filenames.&lt;BR /&gt;However, the attackers could easily change their malicious scripts to have a new hash, or point it to another domain and IP for C2. I'm thus evaluating what other options we'd have to scan for suspicious behaviour, particularly the way the malicious script scans for credentials and exfiltrates the collected information.&lt;BR /&gt;How can we get more information if PaloAlto is already working on such (BIOC) detection rules, and when they will be available?&lt;/P&gt;</description>
      <pubDate>Tue, 24 Mar 2026 09:51:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/up-to-date-detections-for-teampcp-malware-used-in-trivy-and/m-p/1250823#M9215</guid>
      <dc:creator>MarekKreul</dc:creator>
      <dc:date>2026-03-24T09:51:51Z</dc:date>
    </item>
    <item>
      <title>Re: Up-to-date detections for TeamPCP malware used in Trivy and Checkmarx compromises available?</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/up-to-date-detections-for-teampcp-malware-used-in-trivy-and/m-p/1250832#M9216</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/1450776839"&gt;@MarekKreul&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Greetings for the day.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Palo Alto Networks has actively researched and implemented behavioral detection rules for the supply chain attacks targeting CI/CD pipelines, such as&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Aqua Security Trivy&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;and&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Checkmarx KICS&lt;/STRONG&gt;&lt;SPAN&gt;. These attacks are primarily associated with the&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Shai Hulud&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;(or Arrakis) campaign, which utilizes malicious scripts to scan for credentials and perform exfiltration on GitHub Actions runners.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-end="212" data-start="62"&gt;&lt;STRONG data-end="109" data-start="62"&gt;1. Available Detection and Prevention Rules&lt;/STRONG&gt;&lt;BR data-end="112" data-start="109" /&gt;Palo Alto Networks provides several rules to detect and block behaviors associated with this threat:&lt;/P&gt;
&lt;UL data-end="855" data-start="214"&gt;
&lt;LI data-end="648" data-start="214" data-section-id="1er04rk"&gt;&lt;STRONG data-end="248" data-start="216"&gt;Malicious Credential Access:&lt;/STRONG&gt; The rule &lt;CODE data-end="281" data-start="258"&gt;ioc.linux.shaihulud.2&lt;/CODE&gt; is designed to detect activity associated with malicious credential-access tools on Linux systems, specifically targeting GitHub Action runners (e.g., processes running under the &lt;CODE data-end="469" data-start="461"&gt;github&lt;/CODE&gt; user or within &lt;CODE data-end="522" data-start="485"&gt;/usr/local/actions-runner/runsvc.sh&lt;/CODE&gt;). This rule aligns with MITRE ATT&amp;amp;CK techniques T1552 (Unsecured Credentials) and T1555 (Credentials from Password Stores).&lt;/LI&gt;
&lt;LI data-end="855" data-start="650" data-section-id="tk7i21"&gt;&lt;STRONG data-end="680" data-start="652"&gt;Enhanced Blocking Rules:&lt;/STRONG&gt; While the initial rules were released in "report" mode to ensure stability, improved detection rules aimed at blocking this attack were shipped in Content Update (CU) 2060.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P data-end="1052" data-start="862"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-end="1052" data-start="862"&gt;&lt;STRONG data-end="942" data-start="862"&gt;2. Monitoring for Suspicious Behavior (Credential Scanning and Exfiltration)&lt;/STRONG&gt;&lt;BR data-end="945" data-start="942" /&gt;Beyond static IOCs, you can leverage the following Cortex XDR features to hunt for the behaviors described:&lt;/P&gt;
&lt;UL data-end="1814" data-start="1054"&gt;
&lt;LI data-end="1332" data-start="1054" data-section-id="mttdx8"&gt;&lt;STRONG data-end="1104" data-start="1056"&gt;Behavioral Indicators of Compromise (BIOCs):&lt;/STRONG&gt; You can create custom BIOC rules under the Credential Access and Exfiltration categories to monitor for suspicious patterns, such as unusual file reads in credential directories or large data uploads to external IP addresses.&lt;/LI&gt;
&lt;LI data-end="1585" data-start="1334" data-section-id="15bezxz"&gt;&lt;STRONG data-end="1390" data-start="1336"&gt;Cortex Query Language (XQL) and Correlation Rules:&lt;/STRONG&gt; Use XQL to craft specific threat hunting queries for relationship-based events. These queries can be saved as Correlation Rules for continuous, near-real-time monitoring of CI/CD environments.&lt;/LI&gt;
&lt;LI data-end="1814" data-start="1587" data-section-id="1ftnhxs"&gt;&lt;STRONG data-end="1618" data-start="1589"&gt;Analytics BIOCs (ABIOCs):&lt;/STRONG&gt; If enabled, the Analytics engine can detect deviations from baseline behavior, such as a GitHub runner process initiating a network connection or script execution it has never performed before.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P data-end="1857" data-start="1821"&gt;&lt;STRONG data-end="1855" data-start="1821"&gt;===================================&lt;/STRONG&gt;&lt;/P&gt;
&lt;P data-end="1857" data-start="1821"&gt;&lt;STRONG data-end="1855" data-start="1821"&gt;How to Get More Information&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL data-end="2418" data-start="1859"&gt;
&lt;LI data-end="2072" data-start="1859" data-section-id="11j0r68"&gt;&lt;STRONG data-end="1885" data-start="1861"&gt;Check Release Notes:&lt;/STRONG&gt; Monitor the Cortex XDR Analytics Content Release Notes for the latest updates on global BIOC and Analytics rules. Palo Alto Networks typically releases new content roughly once a week.&lt;/LI&gt;
&lt;LI data-end="2255" data-start="2074" data-section-id="9cwt5c"&gt;&lt;STRONG data-end="2097" data-start="2076"&gt;Direct Inquiries:&lt;/STRONG&gt; For specific information on emerging threats or to request detection status, you can contact the research team directly at &lt;A class="decorated-link cursor-pointer" rel="noopener" data-end="2252" data-start="2221" target="_blank"&gt;detections@paloaltonetworks.com&lt;/A&gt;.&lt;/LI&gt;
&lt;LI data-end="2418" data-start="2257" data-section-id="ahlpc4"&gt;&lt;STRONG data-end="2280" data-start="2259"&gt;Unit 42 Research:&lt;/STRONG&gt; Refer to Unit 42's technical briefs for deep dives into specific campaigns like Shai Hulud to understand the exact TTPs being targeted.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;If you feel this has answered your query, please let us know by clicking like and &lt;STRONG&gt;"Mark this as a Solution".&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;BR /&gt;S. Subashkar Sekar&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Mar 2026 14:46:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/up-to-date-detections-for-teampcp-malware-used-in-trivy-and/m-p/1250832#M9216</guid>
      <dc:creator>susekar</dc:creator>
      <dc:date>2026-03-24T14:46:05Z</dc:date>
    </item>
  </channel>
</rss>

