Skip to content

Security Sense

AI Threat Intelligence

  • About
  • Blog
  • Privacy Policy

Tag: data-exposure

Apple to Tighten macOS Full Disk Access Controls Over AI Agent Misuse

Posted on October 5, 2026 by Kyle

Overview

Apple is addressing a significant security risk on macOS related to the Full Disk Access (FDA) permission. Certain AI agents are leveraging FDA in ways that grant them overly broad access to user data, including personal files, emails, messages, and browsing history, often without the user’s full understanding. This initiative aims to close a potential privacy and security gap that could lead to widespread data exposure.

Technical Analysis

  • Vulnerability: Misuse of the macOS Full Disk Access (FDA) permission by applications, specifically AI agents.
  • Mechanism: FDA is a legitimate macOS security feature designed to allow applications (e.g., backup software, antivirus) to access protected user data directories.
  • Exploitation: Developers of some AI agents are requesting and receiving FDA, which then grants their applications unrestricted access to sensitive user data across the system. This access includes /Users/<username>/Library/Mail, /Users/<username>/Library/Messages, Safari history, and other personal files.
  • Prerequisites: The user must grant FDA to the AI agent application. The core issue is that the scope of this permission is often not fully understood by the user, and the application may not explicitly inform the user about the full extent of data it will access.
  • Impact: Unauthorized access to sensitive user data, potential for data exfiltration, privacy violations, and compromise of system integrity if the AI agent is malicious or compromised.

Detection

  • Monitor macOS unified logs for TCC (Transparency, Consent, and Control) database changes related to FDA grants, if available via EDR or audit logs.
  • Review tccutil output or TCC.db for applications with kTCCServiceSystemPolicyAllFiles permission.
  • Behavioral analysis of applications granted FDA: look for unusual file access patterns, excessive reads from sensitive directories (e.g., mail, messages, browser history), or network connections to untrusted destinations.
  • Endpoint Detection and Response (EDR) solutions can track process activity and file access by applications with FDA.

Sigma Detection Rules

⚠️ AI-generated detection rules. These are experimental starting points. Review field names, EventIDs, and logic against your environment’s schema before deploying. Tune to reduce false positives.

macOS Application Accessing Sensitive User Data Directories

title: macOS Application Accessing Sensitive User Data Directories
id: 5a8b3c2d-e1f2-4a3b-9c0d-1e2f3a4b5c6d
status: experimental
description: Detects applications accessing sensitive user data directories on macOS, potentially indicating misuse of Full Disk Access by AI agents or other applications.
logsource:
  product: macos
  service: file_access
detection:
  selection_mail:
    TargetFilename|contains: '/Library/Mail/'
  selection_messages:
    TargetFilename|contains: '/Library/Messages/'
  selection_safari_history:
    TargetFilename|contains: '/Library/Safari/History.db'
  condition: 1 of selection_*
level: high

Mitigations

  1. Review FDA Grants: Regularly audit applications listed under System Settings > Privacy & Security > Full Disk Access. Revoke FDA for any application not explicitly requiring it or for those whose purpose does not justify such broad access.
  2. Exercise Caution with AI Agents: Be highly selective when installing and granting permissions to AI agent applications, especially those requesting FDA. Understand the data access implications before approval.
  3. Monitor for Apple Updates: Apply macOS security updates promptly as Apple implements tighter controls around FDA and AI agent data access.
  4. Least Privilege: Adhere to the principle of least privilege for all applications. Only grant necessary permissions.
  5. Data Minimization: Limit the amount of sensitive data stored locally where possible, especially if using applications that require broad system access.

References

  • https://thehackernews.com/2026/10/apple-plans-tighter-macos-full-disk.html

Indicators of Compromise

No public IOCs available at time of writing.

MITRE ATT&CK

  • T1083 — File and Directory Discovery
🤖 AI Attribution
Generated by gemini-2.5-flash ·
1,533 input / 1,069 output tokens ·
Reviewed and approved by a human analyst before publication
Posted in vulnerabilityTagged ai, critical, data-exposure, macos, privacy, vulnerabilityLeave a comment

AI Coding Agents Expose Internal Company Data on GitHub

Posted on September 30, 2026 by Kyle

Overview

AI coding agents, used by developers for tasks such as code review, have been observed uploading screenshots containing sensitive internal company data to public GitHub repositories. This unintentional exposure has affected over 300 organizations, resulting in more than 13,000 internal images, including customer billing records and screens of unreleased features, becoming publicly accessible. The incidents primarily occurred under developers’ personal GitHub accounts, underscoring a critical data leakage vector introduced by certain AI development tools.

Technical Analysis

The data exposure mechanism involves AI coding agents capturing screenshots of developers’ environments, which include sensitive information, and subsequently uploading these images to public GitHub repositories. When developers instruct these agents to document or share code changes, the agents take screenshots that often encompass more than just the code itself. This can include visible UI elements displaying internal customer data, financial records, or proprietary features under development. The lack of built-in redaction or sanitization capabilities in these AI agents, combined with their integration into public code-sharing platforms, facilitates the inadvertent public disclosure of confidential company information. The exposed data was typically found within repositories associated with individual developer accounts, suggesting a lack of organizational oversight or technical controls over AI agent usage.

Detection

  • Public Repository Monitoring: Implement continuous scanning of public code repositories (e.g., GitHub, GitLab) for company-specific keywords, project names, sensitive data patterns (e.g., regex for PII, financial data formats), or proprietary image metadata that might indicate accidental exposure.
  • Data Loss Prevention (DLP) Alerts: Configure network and endpoint DLP solutions to alert on or block uploads of image files (especially screenshots) containing sensitive content to public cloud storage or code hosting services from developer workstations.
  • Audit AI Agent Usage: Review logs or configurations of AI coding agents used within the organization to understand their data handling practices, particularly concerning screenshot generation and external sharing capabilities.

Mitigations

  1. Policy & Training: Establish clear organizational policies prohibiting the use of AI coding agents for tasks that involve sharing screenshots of sensitive or proprietary information. Conduct mandatory developer training on data handling best practices, emphasizing the risks of AI tool usage and the importance of manual redaction or sanitization before sharing any visual content.
  2. Technical Controls for AI Agents: Evaluate and select AI coding agents that offer robust privacy features, such as automatic redaction of sensitive data in screenshots, granular control over what content is captured, or explicit prompts for user review before sharing externally.
  3. Data Loss Prevention (DLP) Implementation: Deploy and fine-tune endpoint and network DLP solutions to detect and prevent the upload of sensitive image files (e.g., screenshots containing PII, financial data, or intellectual property) to unapproved external services or public repositories.
  4. Access Control Review: Ensure that developers’ access to sensitive internal systems and data is strictly governed by the principle of least privilege, minimizing the amount of confidential information that could be inadvertently exposed in a screenshot.
  5. Regular Security Audits: Conduct periodic security audits of development workflows and tools, including AI agents, to identify and remediate potential data leakage vectors.

References

  • https://thehackernews.com/2026/09/ai-coding-agents-exposed-13000-internal.html

Indicators of Compromise

No public IOCs available at time of writing.

MITRE ATT&CK

  • T1567.002 — Exfiltration to Cloud Storage
🤖 AI Attribution
Generated by gemini-2.5-flash ·
1,540 input / 907 output tokens ·
Reviewed and approved by a human analyst before publication
Posted in vulnerabilityTagged ai, data-exposure, data-leak, github, high, misconfigurationLeave a comment

Cloudflare Containers Cross-Tenant Data Exposure Vulnerability

Posted on September 27, 2026 - September 27, 2026 by Kyle

Overview

Cloudflare has addressed a critical cross-tenant vulnerability affecting its Containers and Sandboxes services. This flaw permitted customers with a Workers Paid account to recover residual data belonging to other customers sharing the same physical host. The vulnerability posed a significant risk of unauthorized data exposure across different Cloudflare tenants.

Technical Analysis

  • The vulnerability resided within Cloudflare’s Containers and Sandboxes environments.
  • It allowed a malicious or compromised Workers Paid account to access residual data left behind by other tenants on the same underlying physical infrastructure.
  • This implies a failure in proper isolation or secure data sanitization between containerized environments.
  • The attack vector required an active Workers Paid account on the Cloudflare platform.
  • Affected services: Cloudflare Containers and Sandboxes.

Detection

  • This vulnerability was an internal platform issue within Cloudflare’s infrastructure.
  • Cloudflare customers cannot directly detect exploitation attempts or successful data recovery related to this specific flaw within their own logs or systems.
  • Customers should monitor Cloudflare’s security advisories and ensure their services are up-to-date.

Mitigations

  1. Cloudflare has already implemented a fix for this vulnerability. Customers using Cloudflare Containers and Sandboxes should ensure their services are operating on the latest patched infrastructure.
  2. Review Cloudflare’s official security advisories and best practices for Workers and Container services.
  3. Implement robust data handling and encryption practices for sensitive data stored or processed within Cloudflare environments, assuming a zero-trust model even within cloud platforms.

References

  • https://www.bleepingcomputer.com/news/security/cloudflare-fixes-containers-cross-tenant-flaw-exposing-customer-data/

Indicators of Compromise

No public IOCs available at time of writing.

MITRE ATT&CK

  • T1530 — Data from Cloud Storage
🤖 AI Attribution
Generated by gemini-2.5-flash ·
1,489 input / 557 output tokens ·
Reviewed and approved by a human analyst before publication
Posted in vulnerabilityTagged cloud, cloudflare, critical, cross-tenant, data-exposure, vulnerabilityLeave a comment
Proudly powered by WordPress | Theme: micro, developed by DevriX.