Loading story…
Meta halted its internal Model Capability Initiative (MCI) after a permissions misconfiguration exposed sensitive employee-monitoring data to the company’s broader workforce. The program, launched in April for U.S.-based employees, collected detailed telemetry including mouse movements, clicks, keystrokes, and occasional screenshots to train internal AI and machine-learning systems. Reuters-reported documents indicated the exposed data included private conversations, AI prompts and request transcripts, and other records gathered from internal systems.
Internal concerns had reportedly been raised earlier about both the intrusiveness of the monitoring and data-storage weaknesses, with a later security alert finding confidential information accessible in cleartext to Meta employees. The exposed material reportedly included named HR performance data and documents classified under DSS sensitivity levels 1 through 4. Meta said it has found no evidence of improper employee access or malicious exploitation, but it suspended the program while investigating and has not said when, or in what form, it may resume.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
6 events from the most recent confirmed update back to the earliest known activity.
In May 2026, Meta employees petitioned against the Model Capability Initiative, raising concerns about privacy protections and the scope of telemetry collection for AI training. The reference says workers questioned the lack of completed privacy reviews and the vagueness of proposed mitigations.
Reuters reported that data storage issues related to the MCI program had already been flagged in May. This preceded discovery that collected confidential data was broadly accessible internally.
An internal security alert determined that confidential MCI training data was accessible in cleartext to any Meta employee because of a permissions misconfiguration. Exposed data reportedly included AI prompts and transcripts, private employee conversations, HR performance data, and documents with DSS sensitivity labels 1 through 4.
Meta began deploying its Model Capability Initiative (MCI) to U.S.-based employees in April 2026 to collect telemetry such as mouse movements, clicks, keystrokes, and occasional screenshots for AI training.
On 2026-06-22, Meta halted the Model Capability Initiative while it investigated the internal exposure of sensitive employee monitoring data. Meta said it had no evidence that employees improperly accessed the data or that the issue involved external malicious exploitation.
Meta said it detected unauthorized internal access to MCI data on 2026-06-18 and fixed the issue within four hours. The company later acknowledged that the initial remediation was incomplete and that additional access restrictions were required.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
9 references tracked. Mallory keeps watching after this page renders.
boingboing.net
Open sourcetomshardware.com
Open sourcepivot-to-ai.com
Open sourcecio.com
Open sourcescworld.com
Open sourcezdnet.fr
Open sourceghacks.net
Open sourcewired.com
Open sourcewired.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Meta disclosed an internal **Sev 1 security incident** after an engineer followed troubleshooting advice generated by an AI agent on an internal forum, causing large volumes of company data to become accessible to unauthorized employees for more than two hours. Reporting cited by *IT Pro* and *The Guardian* said the exposure affected sensitive internal data and spread access beyond the intended group of engineers, raising concerns about how AI-generated operational guidance can directly alter permissions and data handling inside enterprise environments. Meta said an incident occurred but maintained that **no user data was mishandled**. The case has been highlighted as a warning about **agentic AI** in corporate settings, where staff may act on plausible but unsafe recommendations without adequate review. The reporting also underscored broader security issues tied to AI agents, including excessive access, weak validation of automated guidance, and identity governance challenges involving non-human accounts and systems.
Jun 29, 2026
Meta has indefinitely paused work with data contractor Mercor after a major breach at the startup raised concerns that proprietary human-generated training datasets used by leading AI companies may have been exposed. Mercor supplies training data to firms including **OpenAI** and **Anthropic**, and the incident has prompted other AI labs to reevaluate their ties to the company. Mercor confirmed the attack internally on March 31 and said it was linked to a broader incident affecting multiple organizations. The breach is considered especially sensitive because exposed datasets could reveal details about AI model training pipelines and other competitive information. OpenAI said it is investigating whether its proprietary training data was affected, while adding that no OpenAI user data was exposed. Reporting tied the intrusion to compromised versions of the `LiteLLM` AI API tool, with researchers attributing the activity to **TeamPCP** rather than a threat actor simply using the **Lapsus$** name; the disruption also reportedly affected contractor work on Meta-related projects, including **Chordus**.
Jun 29, 2026
Meta suspended its internal Model Capability Initiative after an internal error reportedly made sensitive employee monitoring data broadly accessible inside the company, intensifying criticism of a program that collected workplace activity from tools including Gmail, Google Chat, Meta AI, screenshots, and usage patterns. Meta said it found no evidence of malicious activity or an external breach, but the incident renewed concerns about consent, unencrypted storage, and how far companies are going to feed AI systems with employee data. Similar privacy concerns surfaced in the Netherlands, where a watchdog said the AIVD and MIVD intelligence services mishandled bulk datasets containing personal information through weak controls, excessive retention, and inadequate oversight, raising alarms that AI-assisted analysis could be applied to unlawfully sourced or improperly retained citizen data. At the same time, new reporting and vendor changes underscored how quickly enterprise AI is expanding the attack surface and governance burden. Orca Security said **81.2%** of organizations running AI packages had at least one known vulnerability and that **99.9%** of fixable AI vulnerability alerts remained unpatched, with risks spanning agent frameworks, vector databases, exposed API keys, excessive permissions, weak authentication, and internet-facing services such as Amazon SageMaker, Azure OpenAI, and Google Vertex AI. Microsoft is adding an in-meeting Teams control to disable Copilot, Facilitator, and recap features during sensitive discussions, while broader industry debate has focused on employees oversharing data with AI assistants, the need to govern agent identities and registries, and warnings that AI prompts, memory, and orchestration layers can leak or concentrate proprietary organizational knowledge if enterprises do not retain tight control over access, telemetry, and data handling.
Jul 16, 2026