Return to Threats

ThreatsDay: AI Search Poisoning, AI Coding Tool Leaking Repos, One-Click Code Execution and 13 More Stories

thehackernews.com 2026-09-24 data leakage Critical

What Happened

This week, the dangerous stuff keeps arriving dressed as something boring. An update. A login box. A search answer. A coding tool. A link you have clicked a hundred times before. That is the thread running through the pile. Trusted paths get poisoned. Old bugs find new jobs. AI tools leak more than expected. Fake prompts look real enough. And some attacks barely need an exploit at all — just

Why It Matters

The report says Z.ai’s ZCode coding assistant was found sending users’ local code repositories to Alibaba Cloud servers without consent, while a separate coding CLI reportedly uploaded entire Git repositories to cloud storage. It also describes AI search poisoning that causes assistants to provide fraudulent contact details and login pages. RealGround analysis: organizations using AI coding or search tools should assess data flows, permissions, third-party components, and controls against unauthorized repository disclosure and manipulated AI outputs.

Healthcare Fintech SaaS SMB AI startups

RealGround Analysis

This signal maps to data leakage. Organizations using AI agents, LLM APIs, SaaS integrations, or sensitive data workflows should review whether this class of issue could create unauthorized tool execution, data leakage, weak approval gates, or unmanaged supply-chain exposure.

Recommended Actions

  • Restrict AI agent tool permissions and production write paths.
  • Review sensitive data access across prompts, logs, embeddings, memory, and SaaS integrations.
  • Add human approval workflows for high-impact or state-changing actions.
  • Run prompt injection and indirect prompt injection tests against affected workflows.
  • Document the owner, control gap, and remediation deadline for this risk class.

Source

https://thehackernews.com/2026/09/threatsday-ai-search-poisoning-ai.html

Talk to AI CISO