<?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/" version="2.0">
  <channel>
    <title>Cyber | Insights</title>
    <link>http://144658892.hs-sites-eu1.com/cyber-insights</link>
    <description>Explore more about the issues that matter to you with insights and analysis from Thomas Murray's experts.</description>
    <language>en</language>
    <pubDate>Tue, 17 Nov 2026 11:29:08 GMT</pubDate>
    <dc:date>2026-11-17T11:29:08Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>A New Cold War: Refrigeration Attacks Are Turning Up The Heat On Boards</title>
      <link>http://144658892.hs-sites-eu1.com/cyber-insights/new-cold-war-refrigeration-attacks-are-turning-heat-boards</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="http://144658892.hs-sites-eu1.com/cyber-insights/new-cold-war-refrigeration-attacks-are-turning-heat-boards" title="" class="hs-featured-image-link"&gt; &lt;img src="https://144658892.hs-sites-eu1.com/hubfs/insights/fridge-blurred.jpg" alt="A New Cold War: Refrigeration Attacks Are Turning Up The Heat On Boards" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; Refrigeration cyberattacks across Europe show how operational technology turns digital intrusions into physical losses. Six questions for boards.</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="http://144658892.hs-sites-eu1.com/cyber-insights/new-cold-war-refrigeration-attacks-are-turning-heat-boards" title="" class="hs-featured-image-link"&gt; &lt;img src="https://144658892.hs-sites-eu1.com/hubfs/insights/fridge-blurred.jpg" alt="A New Cold War: Refrigeration Attacks Are Turning Up The Heat On Boards" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; Refrigeration cyberattacks across Europe show how operational technology turns digital intrusions into physical losses. Six questions for boards.  
&lt;img src="https://track-eu1.hubspot.com/__ptq.gif?a=144658892&amp;amp;k=14&amp;amp;r=http%3A%2F%2F144658892.hs-sites-eu1.com%2Fcyber-insights%2Fnew-cold-war-refrigeration-attacks-are-turning-heat-boards&amp;amp;bu=http%253A%252F%252F144658892.hs-sites-eu1.com%252Fcyber-insights&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Cyber Risk Management</category>
      <category>CyberSecurity</category>
      <pubDate>Thu, 05 Nov 2026 09:25:02 GMT</pubDate>
      <author>enquiries@thomasmurray.com (Thomas Murray)</author>
      <guid>http://144658892.hs-sites-eu1.com/cyber-insights/new-cold-war-refrigeration-attacks-are-turning-heat-boards</guid>
      <dc:date>2026-11-05T09:25:02Z</dc:date>
    </item>
    <item>
      <title>You Trusted the Marketplace. That Was the Point. | Malicious Claude Code Extension in Cursor</title>
      <link>http://144658892.hs-sites-eu1.com/cyber-insights/you-trusted-marketplace-was-point-malicious-claude-code-extension-cursor</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="http://144658892.hs-sites-eu1.com/cyber-insights/you-trusted-marketplace-was-point-malicious-claude-code-extension-cursor" title="" class="hs-featured-image-link"&gt; &lt;img src="https://144658892.hs-sites-eu1.com/hubfs/insights/tm-cyber-light-trails-orchid-1008px.jpg" alt="You Trusted the Marketplace. That Was the Point. | Malicious Claude Code Extension in Cursor" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;On the 29th of October, a malicious copy of the Claude Code extension turned up in Cursor’s extension marketplace. Not built by Anthropic, just made to look like it was, same name, right place, version 2.1.313. It was live for about eleven hours and hit up to 5,000 people before it was pulled.&lt;br&gt;&lt;br&gt;What it tried to do was plant a quiet SSH backdoor on the developer’s machine, drop in an attacker’s key labelled “svc-telemetry” so it looked like something boring and legitimate, set up persistence so it survived a reboot, and beacon details back home. The interesting part for me isn’t really the malware though. It’s how it got there.&amp;nbsp;&lt;/p&gt; 
&lt;h3&gt;Nobody got tricked into anything&amp;nbsp;&lt;/h3&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="http://144658892.hs-sites-eu1.com/cyber-insights/you-trusted-marketplace-was-point-malicious-claude-code-extension-cursor" title="" class="hs-featured-image-link"&gt; &lt;img src="https://144658892.hs-sites-eu1.com/hubfs/insights/tm-cyber-light-trails-orchid-1008px.jpg" alt="You Trusted the Marketplace. That Was the Point. | Malicious Claude Code Extension in Cursor" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;On the 29th of October, a malicious copy of the Claude Code extension turned up in Cursor’s extension marketplace. Not built by Anthropic, just made to look like it was, same name, right place, version 2.1.313. It was live for about eleven hours and hit up to 5,000 people before it was pulled.&lt;br&gt;&lt;br&gt;What it tried to do was plant a quiet SSH backdoor on the developer’s machine, drop in an attacker’s key labelled “svc-telemetry” so it looked like something boring and legitimate, set up persistence so it survived a reboot, and beacon details back home. The interesting part for me isn’t really the malware though. It’s how it got there.&amp;nbsp;&lt;/p&gt; 
&lt;h3&gt;Nobody got tricked into anything&amp;nbsp;&lt;/h3&gt;  
&lt;img src="https://track-eu1.hubspot.com/__ptq.gif?a=144658892&amp;amp;k=14&amp;amp;r=http%3A%2F%2F144658892.hs-sites-eu1.com%2Fcyber-insights%2Fyou-trusted-marketplace-was-point-malicious-claude-code-extension-cursor&amp;amp;bu=http%253A%252F%252F144658892.hs-sites-eu1.com%252Fcyber-insights&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Cyber Risk Management</category>
      <category>CyberSecurity</category>
      <pubDate>Mon, 02 Nov 2026 10:05:15 GMT</pubDate>
      <guid>http://144658892.hs-sites-eu1.com/cyber-insights/you-trusted-marketplace-was-point-malicious-claude-code-extension-cursor</guid>
      <dc:date>2026-11-02T10:05:15Z</dc:date>
      <dc:creator>James Thoburn</dc:creator>
    </item>
    <item>
      <title>Binance Hack: $6.3bn Theft Tests Digital Asset Resilience</title>
      <link>http://144658892.hs-sites-eu1.com/cyber-insights/binance-hack-63bn-theft-tests-digital-asset-resilience-0</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="http://144658892.hs-sites-eu1.com/cyber-insights/binance-hack-63bn-theft-tests-digital-asset-resilience-0" title="" class="hs-featured-image-link"&gt; &lt;img src="https://144658892.hs-sites-eu1.com/hubfs/insights/Frame%2034681%20(3).webp" alt="Binance Hack: $6.3bn Theft Tests Digital Asset Resilience" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="http://144658892.hs-sites-eu1.com/cyber-insights/binance-hack-63bn-theft-tests-digital-asset-resilience-0" title="" class="hs-featured-image-link"&gt; &lt;img src="https://144658892.hs-sites-eu1.com/hubfs/insights/Frame%2034681%20(3).webp" alt="Binance Hack: $6.3bn Theft Tests Digital Asset Resilience" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt;  
&lt;img src="https://track-eu1.hubspot.com/__ptq.gif?a=144658892&amp;amp;k=14&amp;amp;r=http%3A%2F%2F144658892.hs-sites-eu1.com%2Fcyber-insights%2Fbinance-hack-63bn-theft-tests-digital-asset-resilience-0&amp;amp;bu=http%253A%252F%252F144658892.hs-sites-eu1.com%252Fcyber-insights&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Cyber Risk Management</category>
      <category>CyberSecurity</category>
      <pubDate>Fri, 30 Oct 2026 10:17:28 GMT</pubDate>
      <author>enquiries@thomasmurray.com (Thomas Murray)</author>
      <guid>http://144658892.hs-sites-eu1.com/cyber-insights/binance-hack-63bn-theft-tests-digital-asset-resilience-0</guid>
      <dc:date>2026-10-30T10:17:28Z</dc:date>
    </item>
    <item>
      <title>How Do You Know What to Patch When the World’s on Fire? Lessons from php2shell</title>
      <link>http://144658892.hs-sites-eu1.com/cyber-insights/how-do-you-know-what-patch-when-worlds-fire-lessons-php2shell</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="http://144658892.hs-sites-eu1.com/cyber-insights/how-do-you-know-what-patch-when-worlds-fire-lessons-php2shell" title="" class="hs-featured-image-link"&gt; &lt;img src="https://144658892.hs-sites-eu1.com/hubfs/insights/shutterstock_2625915793_0.webp" alt="How Do You Know What to Patch When the World’s on Fire? Lessons from php2shell" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;php2shell, the pair of critical PHP flaws disclosed on 21 October 2026, affects almost every PHP installation that serves web requests. The instinct is to patch everything at once. That carries its own risk, and the decision about what to patch first is really made long before a vulnerability lands.&lt;br&gt;&lt;br&gt;I was on a panel recently where this came up, and it has stuck with me because almost every question, however it was phrased, was really the same one underneath: when a critical vulnerability lands, where do I actually start? Not the clever stuff, just the starting point. It’s a fair question, because the honest answer is harder than people expect, and php2shell is a good example of why.&lt;/p&gt; 
&lt;h3&gt;What is php2shell?&lt;/h3&gt; 
&lt;p&gt;php2shell is the name given to two critical remote code execution flaws in the PHP runtime itself, tracked as CVE-2026-109618 and CVE-2026-109619.[1] The first turns PHP’s handling of out-of-memory conditions into code execution. The second abuses internal state that survives after the memory behind it has been freed. Neither needs the attacker to log in.[3]&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="http://144658892.hs-sites-eu1.com/cyber-insights/how-do-you-know-what-patch-when-worlds-fire-lessons-php2shell" title="" class="hs-featured-image-link"&gt; &lt;img src="https://144658892.hs-sites-eu1.com/hubfs/insights/shutterstock_2625915793_0.webp" alt="How Do You Know What to Patch When the World’s on Fire? Lessons from php2shell" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;php2shell, the pair of critical PHP flaws disclosed on 21 October 2026, affects almost every PHP installation that serves web requests. The instinct is to patch everything at once. That carries its own risk, and the decision about what to patch first is really made long before a vulnerability lands.&lt;br&gt;&lt;br&gt;I was on a panel recently where this came up, and it has stuck with me because almost every question, however it was phrased, was really the same one underneath: when a critical vulnerability lands, where do I actually start? Not the clever stuff, just the starting point. It’s a fair question, because the honest answer is harder than people expect, and php2shell is a good example of why.&lt;/p&gt; 
&lt;h3&gt;What is php2shell?&lt;/h3&gt; 
&lt;p&gt;php2shell is the name given to two critical remote code execution flaws in the PHP runtime itself, tracked as CVE-2026-109618 and CVE-2026-109619.[1] The first turns PHP’s handling of out-of-memory conditions into code execution. The second abuses internal state that survives after the memory behind it has been freed. Neither needs the attacker to log in.[3]&lt;/p&gt;  
&lt;img src="https://track-eu1.hubspot.com/__ptq.gif?a=144658892&amp;amp;k=14&amp;amp;r=http%3A%2F%2F144658892.hs-sites-eu1.com%2Fcyber-insights%2Fhow-do-you-know-what-patch-when-worlds-fire-lessons-php2shell&amp;amp;bu=http%253A%252F%252F144658892.hs-sites-eu1.com%252Fcyber-insights&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Cyber Risk Management</category>
      <category>CyberSecurity</category>
      <pubDate>Fri, 23 Oct 2026 11:17:12 GMT</pubDate>
      <guid>http://144658892.hs-sites-eu1.com/cyber-insights/how-do-you-know-what-patch-when-worlds-fire-lessons-php2shell</guid>
      <dc:date>2026-10-23T11:17:12Z</dc:date>
      <dc:creator>James Thoburn</dc:creator>
    </item>
    <item>
      <title>Third-Party Cyber Risk: Five Supplier Failures in One Week</title>
      <link>http://144658892.hs-sites-eu1.com/cyber-insights/third-party-cyber-risk-five-supplier-failures-one-week</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="http://144658892.hs-sites-eu1.com/cyber-insights/third-party-cyber-risk-five-supplier-failures-one-week" title="" class="hs-featured-image-link"&gt; &lt;img src="https://144658892.hs-sites-eu1.com/hubfs/insights/Frame_34678_compressed.jpg" alt="Third-Party Cyber Risk: Five Supplier Failures in One Week" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;In the week to 15 October, a defence contractor's outage stopped every US federal bankruptcy notice, a supplier-managed system spoiled food in hundreds of French supermarkets, and a reseller shipped tampered crypto wallets. None of these organisations was breached through its own front door. Each was hit through someone it trusted.&amp;nbsp;&lt;br&gt;&lt;br&gt;It is the same pattern we saw at ASOS a week earlier. The retailer has since said the attackers posed as a trusted contact to obtain an employee's login, then used it to reach third-party platforms, including the one that sent customers an "ASOS HACKED" push notification.&lt;sup&gt;1&lt;/sup&gt; The same group has since claimed a breech at Air-France-KLM.&lt;sup&gt;2&lt;/sup&gt; &lt;a href="https://cyber.thomasmurray.com/insights/asos-breach-when-customer-messaging-platform-becomes-attack-surface"&gt;Read our analysis of the ASOS breach.&amp;nbsp;&lt;/a&gt;&lt;/p&gt; 
&lt;p&gt;For financial institutions and investors, the lesson is familiar but sharper than ever: your resilience is only as strong as the weakest party with access to your systems, your data or your customers.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="http://144658892.hs-sites-eu1.com/cyber-insights/third-party-cyber-risk-five-supplier-failures-one-week" title="" class="hs-featured-image-link"&gt; &lt;img src="https://144658892.hs-sites-eu1.com/hubfs/insights/Frame_34678_compressed.jpg" alt="Third-Party Cyber Risk: Five Supplier Failures in One Week" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;In the week to 15 October, a defence contractor's outage stopped every US federal bankruptcy notice, a supplier-managed system spoiled food in hundreds of French supermarkets, and a reseller shipped tampered crypto wallets. None of these organisations was breached through its own front door. Each was hit through someone it trusted.&amp;nbsp;&lt;br&gt;&lt;br&gt;It is the same pattern we saw at ASOS a week earlier. The retailer has since said the attackers posed as a trusted contact to obtain an employee's login, then used it to reach third-party platforms, including the one that sent customers an "ASOS HACKED" push notification.&lt;sup&gt;1&lt;/sup&gt; The same group has since claimed a breech at Air-France-KLM.&lt;sup&gt;2&lt;/sup&gt; &lt;a href="https://cyber.thomasmurray.com/insights/asos-breach-when-customer-messaging-platform-becomes-attack-surface"&gt;Read our analysis of the ASOS breach.&amp;nbsp;&lt;/a&gt;&lt;/p&gt; 
&lt;p&gt;For financial institutions and investors, the lesson is familiar but sharper than ever: your resilience is only as strong as the weakest party with access to your systems, your data or your customers.&lt;/p&gt;  
&lt;img src="https://track-eu1.hubspot.com/__ptq.gif?a=144658892&amp;amp;k=14&amp;amp;r=http%3A%2F%2F144658892.hs-sites-eu1.com%2Fcyber-insights%2Fthird-party-cyber-risk-five-supplier-failures-one-week&amp;amp;bu=http%253A%252F%252F144658892.hs-sites-eu1.com%252Fcyber-insights&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Cyber Risk Management</category>
      <category>CyberSecurity</category>
      <pubDate>Mon, 19 Oct 2026 12:23:00 GMT</pubDate>
      <guid>http://144658892.hs-sites-eu1.com/cyber-insights/third-party-cyber-risk-five-supplier-failures-one-week</guid>
      <dc:date>2026-10-19T12:23:00Z</dc:date>
      <dc:creator>Ed Starkie</dc:creator>
    </item>
    <item>
      <title>The Other Half of the Incident Bill: Why Legal and Technical Response Must Move Together</title>
      <link>http://144658892.hs-sites-eu1.com/cyber-insights/other-half-incident-bill-why-legal-and-technical-response-must-move-together</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="http://144658892.hs-sites-eu1.com/cyber-insights/other-half-incident-bill-why-legal-and-technical-response-must-move-together" title="" class="hs-featured-image-link"&gt; &lt;img src="https://144658892.hs-sites-eu1.com/hubfs/insights/Frame%2034682.webp" alt="The Other Half of the Incident Bill: Why Legal and Technical Response Must Move Together" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;h2&gt;Two Responses, One Clock&amp;nbsp;&lt;/h2&gt; 
&lt;p&gt;When a cyber incident breaks, two responses have to start at once. The technical team works to contain the attack and restore systems. In parallel, the business faces decisions with legal consequences. Who should commission the forensic investigation? What gets written down, and by whom? Which regulators, customers and counterparties must be told, and when?&amp;nbsp;&lt;/p&gt; 
&lt;p&gt;Neither workstream can wait for the other. Faster containment limits the damage, and sound legal judgement limits the regulatory exposure and the consequences of future litigation. Our previous article asked whether businesses are better protected or just better insured. This one looks at the legal side of the bill, the part boards most often underestimate, and why packaging it into a warranty with the technical response changes how the first days of an incident plays out.&amp;nbsp;&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="http://144658892.hs-sites-eu1.com/cyber-insights/other-half-incident-bill-why-legal-and-technical-response-must-move-together" title="" class="hs-featured-image-link"&gt; &lt;img src="https://144658892.hs-sites-eu1.com/hubfs/insights/Frame%2034682.webp" alt="The Other Half of the Incident Bill: Why Legal and Technical Response Must Move Together" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;h2&gt;Two Responses, One Clock&amp;nbsp;&lt;/h2&gt; 
&lt;p&gt;When a cyber incident breaks, two responses have to start at once. The technical team works to contain the attack and restore systems. In parallel, the business faces decisions with legal consequences. Who should commission the forensic investigation? What gets written down, and by whom? Which regulators, customers and counterparties must be told, and when?&amp;nbsp;&lt;/p&gt; 
&lt;p&gt;Neither workstream can wait for the other. Faster containment limits the damage, and sound legal judgement limits the regulatory exposure and the consequences of future litigation. Our previous article asked whether businesses are better protected or just better insured. This one looks at the legal side of the bill, the part boards most often underestimate, and why packaging it into a warranty with the technical response changes how the first days of an incident plays out.&amp;nbsp;&lt;/p&gt;  
&lt;img src="https://track-eu1.hubspot.com/__ptq.gif?a=144658892&amp;amp;k=14&amp;amp;r=http%3A%2F%2F144658892.hs-sites-eu1.com%2Fcyber-insights%2Fother-half-incident-bill-why-legal-and-technical-response-must-move-together&amp;amp;bu=http%253A%252F%252F144658892.hs-sites-eu1.com%252Fcyber-insights&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Cyber Risk Management</category>
      <category>CyberSecurity</category>
      <pubDate>Wed, 14 Oct 2026 13:31:34 GMT</pubDate>
      <guid>http://144658892.hs-sites-eu1.com/cyber-insights/other-half-incident-bill-why-legal-and-technical-response-must-move-together</guid>
      <dc:date>2026-10-14T13:31:34Z</dc:date>
      <dc:creator>David Whiteley</dc:creator>
    </item>
    <item>
      <title>The ASOS Breach: When a Customer Messaging Platform Becomes the Attack Surface</title>
      <link>http://144658892.hs-sites-eu1.com/cyber-insights/asos-breach-when-customer-messaging-platform-becomes-attack-surface</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="http://144658892.hs-sites-eu1.com/cyber-insights/asos-breach-when-customer-messaging-platform-becomes-attack-surface" title="" class="hs-featured-image-link"&gt; &lt;img src="https://144658892.hs-sites-eu1.com/hubfs/insights/Frame%2034677.webp" alt="The ASOS Breach: When a Customer Messaging Platform Becomes the Attack Surface" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;div&gt;  
 &lt;div&gt; 
  &lt;div&gt; 
   &lt;p&gt;On the morning of Tuesday 6 October 2026, ASOS customers received a push notification that no retailer wants to send. Headed “ASOS HACKED” and addressed to the company’s data protection officer and IT team, it claimed the company’s Snowflake environment had been compromised and threatened to leak data unless ASOS engaged with the sender. Within hours, screenshots were circulating on social media and ASOS shares had fallen by more than 10%, according to Reuters.&lt;/p&gt; 
  &lt;/div&gt; 
 &lt;/div&gt;  
&lt;/div&gt; 
&lt;div style="width: 540.828px; color: rgba(27, 41, 59, 0.8); background-color: #ffffff;"&gt; 
 &lt;div style="width: 500.828px;"&gt;
   &amp;nbsp; 
 &lt;/div&gt; 
&lt;/div&gt; 
&lt;p&gt;The investigation is ongoing and the picture may look different in a week. But the ASOS breach already carries a clear lesson. The attackers did not need to reach the company’s core systems to create a market-moving event. Access to a third-party customer communications platform was enough.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="http://144658892.hs-sites-eu1.com/cyber-insights/asos-breach-when-customer-messaging-platform-becomes-attack-surface" title="" class="hs-featured-image-link"&gt; &lt;img src="https://144658892.hs-sites-eu1.com/hubfs/insights/Frame%2034677.webp" alt="The ASOS Breach: When a Customer Messaging Platform Becomes the Attack Surface" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;div&gt;  
 &lt;div&gt; 
  &lt;div&gt; 
   &lt;p&gt;On the morning of Tuesday 6 October 2026, ASOS customers received a push notification that no retailer wants to send. Headed “ASOS HACKED” and addressed to the company’s data protection officer and IT team, it claimed the company’s Snowflake environment had been compromised and threatened to leak data unless ASOS engaged with the sender. Within hours, screenshots were circulating on social media and ASOS shares had fallen by more than 10%, according to Reuters.&lt;/p&gt; 
  &lt;/div&gt; 
 &lt;/div&gt;  
&lt;/div&gt; 
&lt;div style="width: 540.828px; color: rgba(27, 41, 59, 0.8); background-color: #ffffff;"&gt; 
 &lt;div style="width: 500.828px;"&gt;
   &amp;nbsp; 
 &lt;/div&gt; 
&lt;/div&gt; 
&lt;p&gt;The investigation is ongoing and the picture may look different in a week. But the ASOS breach already carries a clear lesson. The attackers did not need to reach the company’s core systems to create a market-moving event. Access to a third-party customer communications platform was enough.&lt;/p&gt;  
&lt;img src="https://track-eu1.hubspot.com/__ptq.gif?a=144658892&amp;amp;k=14&amp;amp;r=http%3A%2F%2F144658892.hs-sites-eu1.com%2Fcyber-insights%2Fasos-breach-when-customer-messaging-platform-becomes-attack-surface&amp;amp;bu=http%253A%252F%252F144658892.hs-sites-eu1.com%252Fcyber-insights&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Cyber Risk Management</category>
      <category>CyberSecurity</category>
      <pubDate>Thu, 08 Oct 2026 11:43:24 GMT</pubDate>
      <guid>http://144658892.hs-sites-eu1.com/cyber-insights/asos-breach-when-customer-messaging-platform-becomes-attack-surface</guid>
      <dc:date>2026-10-08T11:43:24Z</dc:date>
      <dc:creator>Ed Starkie</dc:creator>
    </item>
    <item>
      <title>Five Things AI-Assisted Attackers Left Behind</title>
      <link>http://144658892.hs-sites-eu1.com/cyber-insights/five-things-ai-assisted-attackers-left-behind</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="http://144658892.hs-sites-eu1.com/cyber-insights/five-things-ai-assisted-attackers-left-behind" title="" class="hs-featured-image-link"&gt; &lt;img src="https://144658892.hs-sites-eu1.com/hubfs/insights/shutterstock_2512142539.webp" alt="Five Things AI-Assisted Attackers Left Behind" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Over recent months, a growing share of our incident response engagements has had one thing in common: somewhere in the attack chain, the threat actor had been talking to a large language model (LLM). The calls themselves still arrive the way they always have, often late on a Friday, from someone who is calm in the way people are when they are very much not calm, and whose first sentence is some variation of “we think something’s happened”. What has changed is what we find once we start looking.&lt;/p&gt; 
&lt;p&gt;That isn’t a prediction. It’s what we’ve found in the artefacts. Below are five patterns we’ve seen repeatedly across our engagements, and what they mean for defenders.&lt;/p&gt; 
&lt;h4&gt;1. The intruder left the chat log behind&lt;/h4&gt; 
&lt;p&gt;The most striking evidence is also the most mundane. On several engagements this year we have recovered, from staging directories and browser profiles on compromised hosts, the conversation history between the threat actor and an LLM as the intrusion progressed. Not a fragment. The whole thing.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="http://144658892.hs-sites-eu1.com/cyber-insights/five-things-ai-assisted-attackers-left-behind" title="" class="hs-featured-image-link"&gt; &lt;img src="https://144658892.hs-sites-eu1.com/hubfs/insights/shutterstock_2512142539.webp" alt="Five Things AI-Assisted Attackers Left Behind" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Over recent months, a growing share of our incident response engagements has had one thing in common: somewhere in the attack chain, the threat actor had been talking to a large language model (LLM). The calls themselves still arrive the way they always have, often late on a Friday, from someone who is calm in the way people are when they are very much not calm, and whose first sentence is some variation of “we think something’s happened”. What has changed is what we find once we start looking.&lt;/p&gt; 
&lt;p&gt;That isn’t a prediction. It’s what we’ve found in the artefacts. Below are five patterns we’ve seen repeatedly across our engagements, and what they mean for defenders.&lt;/p&gt; 
&lt;h4&gt;1. The intruder left the chat log behind&lt;/h4&gt; 
&lt;p&gt;The most striking evidence is also the most mundane. On several engagements this year we have recovered, from staging directories and browser profiles on compromised hosts, the conversation history between the threat actor and an LLM as the intrusion progressed. Not a fragment. The whole thing.&lt;/p&gt;  
&lt;img src="https://track-eu1.hubspot.com/__ptq.gif?a=144658892&amp;amp;k=14&amp;amp;r=http%3A%2F%2F144658892.hs-sites-eu1.com%2Fcyber-insights%2Ffive-things-ai-assisted-attackers-left-behind&amp;amp;bu=http%253A%252F%252F144658892.hs-sites-eu1.com%252Fcyber-insights&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Cyber Risk Management</category>
      <category>CyberSecurity</category>
      <pubDate>Mon, 28 Sep 2026 13:03:23 GMT</pubDate>
      <guid>http://144658892.hs-sites-eu1.com/cyber-insights/five-things-ai-assisted-attackers-left-behind</guid>
      <dc:date>2026-09-28T13:03:23Z</dc:date>
      <dc:creator>James Thoburn</dc:creator>
    </item>
    <item>
      <title>Warranty or Insurance? Rethinking How Businesses Fund Cyber Risk</title>
      <link>http://144658892.hs-sites-eu1.com/cyber-insights/warranty-or-insurance-rethinking-how-businesses-fund-cyber-risk</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="http://144658892.hs-sites-eu1.com/cyber-insights/warranty-or-insurance-rethinking-how-businesses-fund-cyber-risk" title="" class="hs-featured-image-link"&gt; &lt;img src="https://144658892.hs-sites-eu1.com/hubfs/insights/shutterstock_2393664883%203.webp" alt="Warranty or Insurance? Rethinking How Businesses Fund Cyber Risk" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Boards ask the same question at every renewal: are we actually better protected, or just better insured? Insurance, warranties, monitoring and incident response are increasingly sold in overlapping language, often by the same providers, across UK, US and other markets. Knowing what each one actually does is a governance question, not a procurement detail.&amp;nbsp;&lt;/p&gt; 
&lt;h2&gt;Two Different Instruments&lt;/h2&gt; 
&lt;p&gt;Insurance is third-party tisk transfer. A pool of premiums funds claims, tested against policy wording once a loss has occured. A warranty works differently: It's a first-party promise from the provider of a security service, paying up to a defined cap when a qualifying incident happens. That gives the provider a direct stake in the incident not happening, or being resolved fast.&amp;nbsp;&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="http://144658892.hs-sites-eu1.com/cyber-insights/warranty-or-insurance-rethinking-how-businesses-fund-cyber-risk" title="" class="hs-featured-image-link"&gt; &lt;img src="https://144658892.hs-sites-eu1.com/hubfs/insights/shutterstock_2393664883%203.webp" alt="Warranty or Insurance? Rethinking How Businesses Fund Cyber Risk" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Boards ask the same question at every renewal: are we actually better protected, or just better insured? Insurance, warranties, monitoring and incident response are increasingly sold in overlapping language, often by the same providers, across UK, US and other markets. Knowing what each one actually does is a governance question, not a procurement detail.&amp;nbsp;&lt;/p&gt; 
&lt;h2&gt;Two Different Instruments&lt;/h2&gt; 
&lt;p&gt;Insurance is third-party tisk transfer. A pool of premiums funds claims, tested against policy wording once a loss has occured. A warranty works differently: It's a first-party promise from the provider of a security service, paying up to a defined cap when a qualifying incident happens. That gives the provider a direct stake in the incident not happening, or being resolved fast.&amp;nbsp;&lt;/p&gt;  
&lt;img src="https://track-eu1.hubspot.com/__ptq.gif?a=144658892&amp;amp;k=14&amp;amp;r=http%3A%2F%2F144658892.hs-sites-eu1.com%2Fcyber-insights%2Fwarranty-or-insurance-rethinking-how-businesses-fund-cyber-risk&amp;amp;bu=http%253A%252F%252F144658892.hs-sites-eu1.com%252Fcyber-insights&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Cyber Risk Management</category>
      <category>CyberSecurity</category>
      <pubDate>Tue, 22 Sep 2026 13:23:27 GMT</pubDate>
      <guid>http://144658892.hs-sites-eu1.com/cyber-insights/warranty-or-insurance-rethinking-how-businesses-fund-cyber-risk</guid>
      <dc:date>2026-09-22T13:23:27Z</dc:date>
      <dc:creator>David Whiteley</dc:creator>
    </item>
    <item>
      <title>The Revolut Incident: When Trust Becomes the Attack Surface</title>
      <link>http://144658892.hs-sites-eu1.com/cyber-insights/revolut-incident-when-trust-becomes-attack-surface</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="http://144658892.hs-sites-eu1.com/cyber-insights/revolut-incident-when-trust-becomes-attack-surface" title="" class="hs-featured-image-link"&gt; &lt;img src="https://144658892.hs-sites-eu1.com/hubfs/insights/Frame%2034661%20(2).webp" alt="The Revolut Incident: When Trust Becomes the Attack Surface" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;On 12 September 2026, Revolut confirmed that sensitive customer information had been disclosed to an unauthorised third party following fraudulent requests sent from an email account associated with a legitimate government agency domain. Revolut described the event as a "sophisticated external impersonation scam" and said its systems and customer funds were unaffected.&lt;sup&gt;[1] [2]&amp;nbsp;&lt;/sup&gt;&lt;br&gt;&lt;br&gt;We will see below that the full details of the incident are not yet known, but what makes it particularly interesting is the apparent attack path. Based on what is currently public, the attacker did not need to penetrate Revolut's infrastructure. Instead, they appear to have exploited the trust placed in a legitimate information-request process. For banks, fintechs, payment providers, digital asset businesses and other entities holding valuable identity and transaction information, the distinction is important and offers lessons for their own organisations.&lt;/p&gt; 
&lt;h3&gt;Let's start with what we know&lt;/h3&gt; 
&lt;p&gt;Revolut has confirmed that the fraudulent requests came from an email address on a legitimate government agency domain. It says a "very limited" number of customers were affected, that those customers were notified, that the offending address was blocked, and that the relevant government agency, law enforcement, data-protection authorities and financial regulators were informed.&lt;sup&gt;[1]&lt;/sup&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="http://144658892.hs-sites-eu1.com/cyber-insights/revolut-incident-when-trust-becomes-attack-surface" title="" class="hs-featured-image-link"&gt; &lt;img src="https://144658892.hs-sites-eu1.com/hubfs/insights/Frame%2034661%20(2).webp" alt="The Revolut Incident: When Trust Becomes the Attack Surface" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;On 12 September 2026, Revolut confirmed that sensitive customer information had been disclosed to an unauthorised third party following fraudulent requests sent from an email account associated with a legitimate government agency domain. Revolut described the event as a "sophisticated external impersonation scam" and said its systems and customer funds were unaffected.&lt;sup&gt;[1] [2]&amp;nbsp;&lt;/sup&gt;&lt;br&gt;&lt;br&gt;We will see below that the full details of the incident are not yet known, but what makes it particularly interesting is the apparent attack path. Based on what is currently public, the attacker did not need to penetrate Revolut's infrastructure. Instead, they appear to have exploited the trust placed in a legitimate information-request process. For banks, fintechs, payment providers, digital asset businesses and other entities holding valuable identity and transaction information, the distinction is important and offers lessons for their own organisations.&lt;/p&gt; 
&lt;h3&gt;Let's start with what we know&lt;/h3&gt; 
&lt;p&gt;Revolut has confirmed that the fraudulent requests came from an email address on a legitimate government agency domain. It says a "very limited" number of customers were affected, that those customers were notified, that the offending address was blocked, and that the relevant government agency, law enforcement, data-protection authorities and financial regulators were informed.&lt;sup&gt;[1]&lt;/sup&gt;&lt;/p&gt;  
&lt;img src="https://track-eu1.hubspot.com/__ptq.gif?a=144658892&amp;amp;k=14&amp;amp;r=http%3A%2F%2F144658892.hs-sites-eu1.com%2Fcyber-insights%2Frevolut-incident-when-trust-becomes-attack-surface&amp;amp;bu=http%253A%252F%252F144658892.hs-sites-eu1.com%252Fcyber-insights&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Cyber Risk Management</category>
      <category>CyberSecurity</category>
      <pubDate>Mon, 14 Sep 2026 16:11:16 GMT</pubDate>
      <guid>http://144658892.hs-sites-eu1.com/cyber-insights/revolut-incident-when-trust-becomes-attack-surface</guid>
      <dc:date>2026-09-14T16:11:16Z</dc:date>
      <dc:creator>Ed Starkie</dc:creator>
    </item>
  </channel>
</rss>
