<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CuraSec</title><link>https://curasec.metacog.co.kr/</link><description>Recent content on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 10 Jul 2026 09:49:54 -0500</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/index.xml" rel="self" type="application/rss+xml"/><item><title>AI Agents Expanding Non-Human Identity Attack Surface</title><link>https://curasec.metacog.co.kr/insights/2026-07-10-the-replicant-in-your-directory-ai-agents-and-the-identity-s/</link><pubDate>Fri, 10 Jul 2026 09:49:54 -0500</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-10-the-replicant-in-your-directory-ai-agents-and-the-identity-s/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Useful framing for designing IAM controls around service accounts and API tokens used by AI agents, but no specific vulnerability or action required today.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> Relevant background on how non-human identities complicate visibility and scope of compromise, but no IOCs or detection guidance to act on.&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> As AI agents proliferate in the enterprise, schedule an inventory and governance review of non-human identities this quarter to close ownership and access visibility gaps before they become audit findings.&lt;/li>
&lt;/ul></description></item><item><title>Brain0: audit trail tool for AI-generated code commits</title><link>https://curasec.metacog.co.kr/insights/2026-07-10-brain0-ai-brain0-132/</link><pubDate>Fri, 10 Jul 2026 09:49:54 -0500</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-10-brain0-ai-brain0-132/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Tracks agent prompts behind commits and adds signed provenance attestations — worth evaluating if your team uses AI coding agents, but no active threat requiring immediate action.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Addresses AI agent auditability and DLP exposure in code pipelines — useful context for building a policy around AI-assisted development before it becomes a control gap.&lt;/li>
&lt;/ul></description></item><item><title>Cloudflare: Build your own vulnerability harness</title><link>https://curasec.metacog.co.kr/insights/2026-07-10-build-your-own-vulnerability-harness/</link><pubDate>Fri, 10 Jul 2026 09:49:54 -0500</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-10-build-your-own-vulnerability-harness/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Practical walkthrough on building custom vulnerability harnesses — useful for teams doing fuzzing or exploit research, but no running-system change required today.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>CVE-2026-53359: KVM/x86 Guest-to-Host Escape (PoC Published)</title><link>https://curasec.metacog.co.kr/insights/2026-07-10-januscape-guest-to-host-escape-in-kvm-x86-cve-2026-53359/</link><pubDate>Fri, 10 Jul 2026 09:49:54 -0500</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-10-januscape-guest-to-host-escape-in-kvm-x86-cve-2026-53359/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> Public PoC exists for a guest-to-host VM escape in KVM/x86, meaning any Linux host running KVM hypervisors is potentially exposed; patch your kernel to a fixed version once available and audit whether untrusted VMs run on shared KVM hosts.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No active exploitation or IOCs reported yet; monitor for exploitation activity targeting KVM hosts, but no detection work is actionable until TTPs or exploitation patterns emerge.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> CVE-2026-53359 — CISA KEV: not listed, EPSS 0.00, public PoC on GitHub&lt;/li>
&lt;/ul></description></item><item><title>GigaWiper: Destructive Backdoor Combines Multiple Malware Families</title><link>https://curasec.metacog.co.kr/insights/2026-07-10-gigawiper-anatomy-of-a-destructive-backdoor-assembled-from-m/</link><pubDate>Fri, 10 Jul 2026 09:49:54 -0500</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-10-gigawiper-anatomy-of-a-destructive-backdoor-assembled-from-m/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> No exploitation signals or affected software components named in this summary; the analysis may inform future hardening decisions but requires no immediate patch or configuration change.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Plan:&lt;/strong> Microsoft&amp;rsquo;s technical breakdown likely includes TTPs and behavioral indicators — review the full post to extract detection logic for wiper-style activity (e.g., mass file destruction, MBR overwrites) and build or tune relevant Sigma/KQL rules this quarter.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Destructive wiper campaigns can trigger material-incident thresholds; file this analysis for context if a similar attack surfaces in your sector, but no immediate leadership action is warranted without active targeting evidence.&lt;/li>
&lt;/ul></description></item><item><title>HTML phishing attachments use comment stuffing to evade AI detection</title><link>https://curasec.metacog.co.kr/insights/2026-07-10-comment-stuffing-in-an-html-phishing-attachment-as-a-mechani/</link><pubDate>Fri, 10 Jul 2026 09:49:54 -0500</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-10-comment-stuffing-in-an-html-phishing-attachment-as-a-mechani/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Comment stuffing in HTML attachments is a novel obfuscation technique worth understanding when tuning email security tooling or evaluating AI-based scanning products; no patch or config change required.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Plan:&lt;/strong> Build or tune email-gateway detections to flag HTML attachments with abnormally high comment-to-content ratios, as this technique is designed specifically to bypass AI-based filters your stack may rely on.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>Krebs: Offensive cyber startup run by convicted felons pitching zero-day buys</title><link>https://curasec.metacog.co.kr/insights/2026-07-10-felons-fraudsters-flog-offensive-cybersecurity-startup/</link><pubDate>Fri, 10 Jul 2026 09:49:54 -0500</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-10-felons-fraudsters-flog-offensive-cybersecurity-startup/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> Highlights the risk of sourcing threat intel or vulnerability data from unvetted offensive security vendors; useful context when evaluating new tool or feed vendors.&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> Review any vendor relationships or zero-day acquisition programs for due-diligence gaps; this case illustrates how fraudulent operators can enter the security supply chain under assumed identities.&lt;/li>
&lt;/ul></description></item><item><title>MODBEACON RAT Uses gRPC C2; Linked to China's Silver Fox Group</title><link>https://curasec.metacog.co.kr/insights/2026-07-10-new-modbeacon-rat-uses-grpc-streaming-for-encrypted-c2-traff/</link><pubDate>Fri, 10 Jul 2026 09:49:54 -0500</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-10-new-modbeacon-rat-uses-grpc-streaming-for-encrypted-c2-traff/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> gRPC-based C2 may evade TLS inspection tuned for HTTP/2 REST traffic; review whether your egress controls decode and inspect gRPC streams.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Plan:&lt;/strong> Build or tune detections for outbound gRPC streaming to novel external endpoints; Silver Fox distributes via SEO-poisoned counterfeit installers, so hunt for unexpected Rust-compiled binaries in user-facing application paths.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Adds to the picture of China-linked actors targeting enterprise software supply chains via SEO poisoning; useful context for board-level threat landscape briefings but no immediate action required.&lt;/li>
&lt;/ul></description></item><item><title>Three Patched OpenClaw AI Assistant Flaws Enable Host Takeover via WhatsApp</title><link>https://curasec.metacog.co.kr/insights/2026-07-10-researcher-details-whatsapp-to-host-attack-chain-using-three/</link><pubDate>Fri, 10 Jul 2026 09:49:54 -0500</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-10-researcher-details-whatsapp-to-host-attack-chain-using-three/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> If OpenClaw is deployed in your environment, verify you are running a patched version addressing all three CVEs (GHSA-hjr6-g723-hmfm and siblings); no public PoC or KEV listing present, so patch within normal cycle but prioritize given CVSS 8.8 and the RCE/privilege-escalation chain.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No published IOCs or active exploitation reported; the attack chain description (WhatsApp input → credential theft → privilege escalation → host RCE) is worth understanding to recognize behavioral indicators if OpenClaw is in scope, but no detection work is actionable today.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>US delays DeepSeek blacklist amid 100+ firms flagged as security risks</title><link>https://curasec.metacog.co.kr/insights/2026-07-10-us-holds-off-blacklisting-deepseek-more-than-100-firms-deeme/</link><pubDate>Fri, 10 Jul 2026 09:49:54 -0500</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-10-us-holds-off-blacklisting-deepseek-more-than-100-firms-deeme/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> If your org uses DeepSeek or any of the flagged firms, assess vendor risk now before a formal blacklist forces an abrupt cutover; track regulatory status this quarter to avoid a rushed transition.&lt;/li>
&lt;/ul></description></item><item><title>Zimbra Classic Web Client critical XSS flaw requires patching</title><link>https://curasec.metacog.co.kr/insights/2026-07-10-zimbra-urges-customers-to-patch-critical-web-client-xss-flaw/</link><pubDate>Fri, 10 Jul 2026 09:49:54 -0500</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-10-zimbra-urges-customers-to-patch-critical-web-client-xss-flaw/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> Critical XSS in Zimbra Classic Web Client affects organizations running on-prem Zimbra Collaboration; no KEV listing or public PoC in enrichment signals, so patch on your normal critical cycle — apply the vendor-supplied update to your Zimbra instance this sprint.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>About CuraSec</title><link>https://curasec.metacog.co.kr/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://curasec.metacog.co.kr/about/</guid><description>&lt;h2 id="what-this-is">What this is&lt;/h2>
&lt;p>CuraSec is a daily, AI-curated security intelligence channel. Most security
news tells you &lt;em>what happened&lt;/em>; CuraSec tells you &lt;strong>who should do what, now&lt;/strong> —
every item gets three independent verdicts, one per practitioner persona:&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Persona&lt;/th>
 &lt;th>Judged on&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>&lt;strong>Engineer&lt;/strong> (Cloud/AppSec)&lt;/td>
 &lt;td>patching, configuration changes, dependency impact&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>SOC/IR&lt;/strong> (Analyst/Hunter)&lt;/td>
 &lt;td>detections, IOC sweeps, hunting priorities&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Leader&lt;/strong> (CISO/Security Director)&lt;/td>
 &lt;td>policy, vendor risk, board/customer communication&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="the-verdicts">The verdicts&lt;/h2>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Verdict&lt;/th>
 &lt;th>Meaning&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>&lt;strong>Act&lt;/strong>&lt;/td>
 &lt;td>do or check something now (KEV-listed, actively exploited, urgent)&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Plan&lt;/strong>&lt;/td>
 &lt;td>review within the quarter (patch cycles, policy shifts, new techniques)&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Learn&lt;/strong>&lt;/td>
 &lt;td>worth knowing, no action required&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Skip&lt;/strong>&lt;/td>
 &lt;td>not published — marketing, duplicates, irrelevant items&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;p>Items judged Skip for &lt;em>all three&lt;/em> personas are never published.&lt;/p></description></item><item><title>Corrections</title><link>https://curasec.metacog.co.kr/corrections/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://curasec.metacog.co.kr/corrections/</guid><description>&lt;p>Confirmed misjudgments are logged here permanently — the original post gets a
correction note, and the error stays on this page. Format:&lt;/p>
&lt;blockquote>
&lt;p>&lt;strong>YYYY-MM-DD — [post title]&lt;/strong> — what was wrong, what the verdict should have
been, and why the error happened.&lt;/p>&lt;/blockquote>
&lt;h2 id="log">Log&lt;/h2>
&lt;p>&lt;em>No corrections yet. If you spot a bad verdict, please
&lt;a href="https://github.com/jeonck/curasec/issues">open an issue&lt;/a>.&lt;/em>&lt;/p></description></item></channel></rss>