<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[ThreatsDay: AI Search Poisoning, AI Coding Tool Leaking Repos, One-Click Code Execution and 13 More Stories]]></title><description><![CDATA[<p dir="auto">This week's threat landscape is a reminder that trusted paths are often the easiest ones to poison. Whether it's an update prompt, a login box, a search result, or a coding assistant, attackers keep finding ways to dress dangerous payloads as routine interactions. A few themes stand out: old bugs being repurposed, AI tools leaking more than users expect, and fake prompts that look legitimate enough to fool careful users.</p>
<p dir="auto">Some attacks barely require an exploit at all — just a convincing link or a familiar workflow is enough to trigger one-click code execution. Search poisoning tied to AI tools is also gaining traction, alongside incidents where AI coding assistants have leaked repositories. The takeaway is consistent: anything that shortcuts trust is worth a second look.</p>
<p dir="auto">Key points worth noting:</p>
<ul>
<li>AI search results are being poisoned to steer users toward malicious content</li>
<li>AI coding tools have leaked repository data</li>
<li>One-click code execution remains a viable attack path without a traditional exploit</li>
<li>Older vulnerabilities continue to be repurposed in new campaigns</li>
</ul>
<p dir="auto">If your organization relies on AI-assisted search or coding tools, review how those tools handle trust boundaries and what data they can access. Assume that anything surfaced by an AI layer can be manipulated, and verify before acting.</p>
<p dir="auto">Source: <a href="https://thehackernews.com/2026/09/threatsday-ai-search-poisoning-ai.html" target="_blank" rel="noopener noreferrer nofollow ugc">info@thehackernews.com (The Hacker News)</a></p>
<p dir="auto">Does your organization use AI coding or search tools, and how are you handling the trust and data exposure risks they introduce?</p>
]]></description><link>https://xploitlk.com/topic/456/threatsday-ai-search-poisoning-ai-coding-tool-leaking-repos-one-click-code-execution-and-13-more-stories</link><generator>RSS for Node</generator><lastBuildDate>Tue, 27 Oct 2026 10:38:18 GMT</lastBuildDate><atom:link href="https://xploitlk.com/topic/456.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 25 Sep 2026 02:30:29 GMT</pubDate><ttl>60</ttl></channel></rss>