<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ai-Ml on CuraSec</title><link>https://curasec.metacog.co.kr/tags/ai-ml/</link><description>Recent content in Ai-Ml on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 10 Aug 2026 13:39:41 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/ai-ml/index.xml" rel="self" type="application/rss+xml"/><item><title>LoRAScan: Runtime detection of backdoored LoRA adapters via activation spikes</title><link>https://curasec.metacog.co.kr/insights/2026-08-10-lorascan-detecting-backdoor-prompts-in-low-rank-adapters-for/</link><pubDate>Mon, 10 Aug 2026 13:39:41 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-10-lorascan-detecting-backdoor-prompts-in-low-rank-adapters-for/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Identifies a real supply-chain risk for teams consuming third-party LoRA adapters: a backdoored adapter can alter model output on hidden triggers without modifying base model weights. LoRAScan&amp;rsquo;s inference-time monitoring approach is worth evaluating if your ML pipelines pull adapters from untrusted registries or Hugging Face.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No active exploitation, IOCs, or ATT&amp;amp;CK-mappable TTPs to act on; this is foundational research on a threat class. Worth filing as context if your org is building detections around AI/ML pipeline integrity, but no hunt or rule work warranted today.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Surfaces an emerging supply-chain risk category for AI workloads—untrusted fine-tuned adapters as a malware vector—useful background for shaping AI vendor-risk policy before it becomes a control requirement.&lt;/li>
&lt;/ul></description></item><item><title>Hugging Face Diffusers Flaws Enable Arbitrary Code via Model Repos</title><link>https://curasec.metacog.co.kr/insights/2026-08-03-hugging-face-diffusers-flaws-could-let-model-repositories-ex/</link><pubDate>Mon, 03 Aug 2026 13:48:19 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-03-hugging-face-diffusers-flaws-could-let-model-repositories-ex/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> If your pipelines load Hugging Face Diffusers models, audit which model repos are consumed and pin to reviewed/trusted sources; check whether you are on the patched Diffusers version once fixes land, as these flaws bypass the trust_remote_code safeguard.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No active exploitation or IOCs reported; understand that model-loading in ML pipelines can be a code-execution vector and begin thinking about detection coverage for anomalous process spawning from Python ML workloads.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Illustrates that AI/ML supply chain risk is not theoretical — if your teams consume external model repositories, ask whether a policy governing approved model sources exists before a control is needed.&lt;/li>
&lt;/ul></description></item></channel></rss>