<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>MacOS Applications — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/macos-applications/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Fri, 15 May 2026 10:37:19 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/macos-applications/feed.xml" rel="self" type="application/rss+xml"/><item><title>OpenAI Compromised via TanStack Supply Chain Attack</title><link>https://feed.craftedsignal.io/briefs/2026-05-openai-tanstack-supply-chain/</link><pubDate>Fri, 15 May 2026 10:37:19 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-openai-tanstack-supply-chain/</guid><description>OpenAI was impacted by the TanStack supply chain attack, resulting in two employee devices being compromised and the exfiltration of credential material from internal source code repositories.</description><content:encoded><![CDATA[<p>On May 11, 2026, the open-source web application development stack TanStack was compromised, leading to a coordinated campaign that saw over 170 packages across NPM and PyPI namespaces being infected. The TeamPCP hacking group exploited weaknesses in the package publishing process to release 84 malicious artifacts across 42 packages, resulting in developer devices being infected with the Shai-Hulud worm. OpenAI was one of the affected organizations, with two employee devices being compromised, leading to the exfiltration of credentials and other secrets from internal source code repositories. Although the scope of the compromise was limited, the attackers gained access to several internal source code repositories.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The TeamPCP group exploited vulnerabilities in the TanStack package publishing process.</li>
<li>Malicious artifacts were released across 42 packages, resulting in 84 malicious packages.</li>
<li>Over 170 packages across several high-profile NPM and PyPI namespaces were compromised.</li>
<li>Developer devices were infected with the Shai-Hulud worm.</li>
<li>Two OpenAI employee devices were infected as part of the supply chain attack.</li>
<li>Credential material was exfiltrated from internal source code repositories.</li>
<li>Attackers gained access to code-signing certificates for iOS, macOS, Windows, and Android products.</li>
<li>OpenAI is revoking certificates and re-signing applications to mitigate the impact.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>The compromise of two OpenAI employee devices resulted in the exfiltration of credential material, including code-signing certificates for iOS, macOS, Windows, and Android products. Although no customer data or intellectual property was affected, OpenAI is revoking the compromised certificates and requiring macOS users to update their applications by June 12, 2026, to prevent the potential distribution of fake applications. Failure to update macOS applications will result in the products ceasing to receive updates and potentially malfunctioning.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Monitor for unauthorized use of code-signing certificates related to OpenAI products (macOS applications, iOS, macOS, Windows, Android products) on internal networks.</li>
<li>Deploy the Sigma rule detecting Shai-Hulud worm-related activity to identify potential infections within the environment.</li>
<li>Review notarization logs for software signed using previous OpenAI certificates to confirm no unauthorized modifications have occurred, as mentioned in the overview.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">threat</category><category>supply-chain</category><category>credential-access</category><category>npm</category><category>pypi</category></item></channel></rss>