<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Notepad++ supply-chain incident - SecTeer impact assessment]]></title><description><![CDATA[<p dir="auto">The reported Notepad++ supply-chain incident, as described in public reporting, was limited to the application’s built-in auto-update mechanism.</p>
<p dir="auto">SecTeer VulnDetect does not use or depend on the Notepad++ auto-updater. All Notepad++ packages distributed through SecTeer are downloaded directly from the official vendor source and processed through SecTeer’s own validation pipeline.</p>
<p dir="auto">This includes:</p>
<ul>
<li>Verification of the Authenticode signature where the vendor provides signed binaries</li>
<li>Malware scanning using Microsoft Defender</li>
<li>Additional reputation-based checks as a supplementary control</li>
</ul>
<p dir="auto">SecTeer packages are released independently of the vendor’s auto-update channel and are not delivered through the update mechanism involved in the reported incident. As a result, SecTeer did not distribute compromised code, and SecTeer’s distribution infrastructure was not impacted.</p>
<p dir="auto">A system could only have received the compromised update if the built-in Notepad++ auto-update feature was enabled on the system</p>
<p dir="auto">In short: SecTeer’s update mechanism was not involved in the incident, and no compromised Notepad++ packages were delivered through the SecTeer platform.</p>
]]></description><link>https://vulndetect.org/topic/2761/notepad-supply-chain-incident-secteer-impact-assessment</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Mar 2026 05:48:50 GMT</lastBuildDate><atom:link href="https://vulndetect.org/topic/2761.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 03 Feb 2026 09:17:44 GMT</pubDate><ttl>60</ttl></channel></rss>