<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Llmjacking on CuraSec</title><link>https://curasec.metacog.co.kr/tags/llmjacking/</link><description>Recent content in Llmjacking on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 28 Sep 2026 18:35:17 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/llmjacking/index.xml" rel="self" type="application/rss+xml"/><item><title>Infostealers Expose AI Credentials Across 80,000+ Corporate Domains</title><link>https://curasec.metacog.co.kr/insights/2026-09-28-80-000-organizations-had-ai-logins-stolen-from-shadow-ai-to/</link><pubDate>Mon, 28 Sep 2026 18:35:17 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-09-28-80-000-organizations-had-ai-logins-stolen-from-shadow-ai-to/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> Shadow AI usage is creating an unmanaged credential surface; audit all AI API keys and service tokens in use, identify unauthorized AI tool adoption across the org, and enforce MFA on sanctioned AI platforms this quarter.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Plan:&lt;/strong> Build or tune detections for infostealer activity on endpoints that may have accessed AI services, and add AI credential misuse (unexpected API spending, off-hours LLM calls) to your hunting checklist — no specific IOCs are provided but the campaign scale justifies coverage.&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> The breadth of exposed corporate domains signals a shadow-AI governance gap; prioritize an AI tool inventory and acceptable-use policy this quarter, and check whether your domain appears in dark-web credential feeds via your threat intel vendor.&lt;/li>
&lt;/ul></description></item></channel></rss>