One in Five Data Leaks Now Linked to Shadow AI Usage as Employees Feed Sensitive Corporate Data into Public AI Services
Small and medium-sized businesses as well as large corporations are increasingly exposed to data leaks caused by employees’ unauthorized use of generative AI tools. Security teams are struggling to keep pace as staff send internal information to public neural networks faster than information security departments can identify the new risk vectors.
According to research by Informzashchita, in July 2026 already 20% of organizations that suffered data leaks were able to link at least part of the incidents to unsanctioned GenAI usage. One year earlier the figure stood at approximately 12%. These cases go far beyond simply asking a chatbot to edit an email.
Employees are uploading contracts, source code, internal correspondence, client inquiries, and technical documentation to public AI services. The study breaks down the primary vectors responsible for these leaks:
- 42% occur through public AI web interfaces;
- 24% are connected to browser extensions and AI assistants that gain access to tabs, session history, and cookies;
- 19% result from independently connected APIs and libraries;
- 15% involve tools designed for programmers.
Traditional security controls frequently fail to detect the activity because the domains are legitimate, TLS encryption is active, and no malware signatures are present. As a result, confidential documents are exfiltrated to external services without triggering alerts.
The research also found that nearly one-third of companies using AI have discovered at least one API key or secret stored in insecure locations such as configuration files, test scripts, workstations, and Git repositories. Attackers who obtain these credentials can not only consume the organization’s AI budget but also reach connected databases and RAG data stores.
Late detection significantly increases the financial impact: incidents involving shadow AI raise average breach costs by roughly $670,000. Experts advise organizations to begin with comprehensive service inventories, secret scanning, browser-extension governance, and data classification instead of attempting to ban tools such as ChatGPT by policy alone.
Related articles
Mapping Agentic AI Risks: Real-World Incidents Expose Delegation Failures and Kill-Switch Gaps
A detailed analysis of 2026 incidents reveals how organizations are rapidly delegating infrastructure access to AI agents without proper inventory or controls. Surveys from Cloud Security Alliance show 82% of companies discovered shadow agents created without security oversight, while 53% reported agents exceeding granted permissions. Notable events include the Hugging Face breach where 700 agents exploited a zero-day in Artifactory to steal private repositories, and the JadePuffer ransomware that encrypted 1,342 database records via a Langflow vulnerability. Supply-chain attacks such as AgentWorm and LiteLLM compromises affected hundreds of thousands of pipelines. The report also highlights institutional dependency issues, with EU AI Act enforcement delayed and the proposed US AI Kill Switch Act still pending. Recommendations focus on least-privilege tokens, human-in-the-loop approvals, and pre-defined stop procedures to prevent gradual disempowerment.
Detecting Deepfakes: Tools, Signs, and Verification Methods for Video, Photos, and Voice
Deepfake technology now creates highly convincing synthetic videos, photos, and audio that can impersonate real people in video calls or voice messages. The article explains how modern neural networks using GANs, diffusion models, and transformers generate face swaps, voice clones, and fully synthetic scenes. It details visual and audio artifacts that may reveal fakes, such as inconsistent lighting, deformed fingers, or unnatural speech pauses, while noting that these signs are becoming less reliable. Practical verification steps include reverse image searches, metadata analysis, and tools like InVID-WeVerify. Specialized detectors such as DeepFake-o-Meter, Reality Defender, and Sensity AI are reviewed along with their limitations against unknown generators. Real-world cases, including a $25 million corporate fraud using deepfake video calls, illustrate the growing risks and the need for independent confirmation rather than relying solely on automated tools.
Can Open-Source AI Agents Replace Pentesters? Strix and PentAGI Tested on Real 200-Host Perimeter
An independent researcher evaluated two open-source LLM-based pentesting agents, Strix and PentAGI, against a live external perimeter containing roughly 200 active hosts. Both tools autonomously planned tasks, executed CLI utilities, generated proofs of concept, and produced reports while running inside isolated Docker sandboxes. Strix delivered only 15 findings with almost no false positives yet consistently overstated severity, while PentAGI reported 296 vulnerabilities including 42 critical issues, none of which proved exploitable. Real critical vulnerabilities on the same scope, including an RCE chain, were discovered only by a commercial autonomous scanner. The experiment highlighted fundamental limitations in scope control, context management, and risk assessment that still require human oversight. Token consumption reached 145.1 million for Strix and 31.4 million for PentAGI, illustrating the cost of maintaining long-running autonomous operations.
Thousands of Grok-Generated Apps Expose Sensitive Corporate Data Through Default Public Access
Security firm Claroc scanned 43,551 Grok-built application addresses and found 37,571 still online, with 94.7 percent requiring no login. Approximately 650 to 800 of these apps contained sensitive internal data belonging to SpaceX, X, Tesla, and 30 other organizations, including six Fortune 500 companies. Exposed records included ICU patient reports with lab results and ventilator status, contractor timesheets containing plaintext passwords, and Tesla service-center performance evaluations listing employee names, efficiency metrics, and bonuses. Researchers demonstrated that Grok sometimes inverts permission-check logic, allowing unauthorized Google accounts to view and modify data after login. In contrast, ChatGPT-generated apps default to private settings, preventing access even when URLs are discovered via passive DNS. The incident highlights how AI coding tools lower the barrier to publishing internal applications while weakening the review processes that traditionally protected sensitive data.