<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Software-Update on CuraSec</title><link>https://curasec.metacog.co.kr/tags/software-update/</link><description>Recent content in Software-Update on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 20 Oct 2026 15:39:31 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/software-update/index.xml" rel="self" type="application/rss+xml"/><item><title>AOMEI update servers hijacked to distribute malware via backup software</title><link>https://curasec.metacog.co.kr/insights/2026-10-20-hackers-hijack-aomei-update-servers-to-secretly-spread-malwa/</link><pubDate>Tue, 20 Oct 2026 15:39:31 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-20-hackers-hijack-aomei-update-servers-to-secretly-spread-malwa/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> If AOMEI backup products are in your environment, audit endpoints that ran the software during the compromise window for malware indicators and verify current update server integrity; no KEV or PoC signals yet to escalate to Act.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Act:&lt;/strong> Sweep endpoints running AOMEI backup software for unexpected processes or outbound connections spawned during the compromise window; hunt for lateral movement from hosts where the promotional feature may have delivered a payload.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> A reminder that backup and recovery tooling is an attractive supply-chain vector; no broad systemic impact confirmed yet, but file for vendor risk review discussions around update-mechanism security in critical software.&lt;/li>
&lt;/ul></description></item></channel></rss>