<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Lazarus on CuraSec</title><link>https://curasec.metacog.co.kr/tags/lazarus/</link><description>Recent content in Lazarus on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 22 Oct 2026 15:52:23 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/lazarus/index.xml" rel="self" type="application/rss+xml"/><item><title>Lazarus Group Adopts Post-Quantum Crypto in Malware Delivery</title><link>https://curasec.metacog.co.kr/insights/2026-10-22-lazarus-hackers-use-post-quantum-cryptography-for-malware-de/</link><pubDate>Thu, 22 Oct 2026 15:52:23 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-22-lazarus-hackers-use-post-quantum-cryptography-for-malware-de/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> A top-tier nation-state actor integrating PQC into payload delivery may eventually require reassessing TLS inspection and endpoint detection capabilities, but no specific software vulnerability or configuration change is indicated today.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No IOCs, ATT&amp;amp;CK mappings, or detection-ready artifacts are provided; monitor for follow-on reporting with PQC-obfuscated C2 indicators before tuning rules.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Lazarus&amp;rsquo;s operational use of post-quantum cryptography signals growing adversary sophistication — useful context for board threat-landscape briefings, but no immediate vendor exposure or disclosure action is triggered.&lt;/li>
&lt;/ul></description></item></channel></rss>