Skip to content

Back to the record

Feb 26, 2025Confirmed

Microsoft Copilot Reportedly Able to Access Cached Data from Since-Private GitHub Repositories

Rogue: Caused harmAI loose in the worldData exfiltrationDERIVED

Approved by person, Oct 11, 2026. How entries are approved

Showing full summaries.

Lasso Security reported that Microsoft Copilot could return content from GitHub repositories that had been public briefly but later set to private or deleted. Lasso attributed this to Bing's caching system, which stored "zombie data" from over 20,000 repositories. The cached content allegedly included sensitive information such as access keys, tokens, and internal packages. Microsoft reportedly classified the issue as low severity and applied only partial mitigations.

What this means for youAt home and at work, anything once posted publicly, even briefly, may stay retrievable through AI tools, so keys or passwords posted by mistake must be treated as leaked and replaced. Governments and companies should expect AI search tools to expose old cached data. Check any code you have published, and rotate any keys or tokens that were ever public.

Sources

Data from the AI Incident Database (incidentdatabase.ai), licensed CC BY-SA 4.0 (https://creativecommons.org/licenses/by-sa/4.0/). McGregor, S. (2021) Preventing Repeated Real World AI Failures by Cataloging Incidents: The AI Incident Database. IAAI-21.

Source data license: CC BY-SA 4.0 (database). Report contents keep their own rights; reports.text, submissions, images and videos are excluded from the data license.

rogue:R4

Covered by snapshot 45

da93f03b406f409940d0a6ef47b526607f82ebf457d98f69299b88aceede576a

This entry is record number 2036. It has not been edited since it was approved; the hash above would not match if it had. How to verify

Microsoft Copilot Reportedly Able to Access Cached Data from Since-Private GitHub Repositories | Vigilo AI Watch