{"meta":{"exportedAt":"2026-10-23T08:50:07.290Z","formatVersion":2,"selection":{"q":"eu","system":"","harm":"","context":"","country":"","role":"","relation":"contextual","evidence":"","year":"2026","response":"","severity":"","verification":"","view":"incidents","sort":"added"},"totalIncidents":4,"coverage":{"cases":4,"countries":3,"languages":3,"unknownLocation":1,"locationPending":0,"unknownLanguage":0,"unknownDate":0,"lawsuits":0,"regulatory":0,"minors":1,"coreRelations":0,"contextualRelations":4,"mixedRelations":0,"unknownRelations":0,"relationPending":0,"relationUnknown":0},"countingNote":"Distinct public cases in this selection. People counts apply within individual cases only; cross-case person overlap has not been resolved. No population incidence estimate.","affectedCountNote":"Interpret person counts with affectedCountStatus and the reported effects. Unquantified zeros are placeholders, not a measured zero.","source":"AI incidents","publisher":"NOPE","url":"https://nope.net/incidents","license":"CC BY 4.0"},"incidents":[{"id":"2026-zhejiang-toddler-ai-asthma-diagnosis-mother-declined-chest-xray-pneumonia-hospitalised","caseFacts":{"claims":[{"id":"c1","status":"reported","evidence":[{"locator":"'今年8月，浙江一名3岁男童阳阳（化名）的案例令人警醒。阳阳有哮喘病史，妈妈在AI上输入“过敏、哮喘、咳嗽、夜间咳喘”等关键词，AI快速给出“支气管哮喘急性发作”的诊断'","relation":"supports","source_id":"s1"}],"assertion":"In August 2026 the mother of a three-year-old boy with a history of asthma in Zhejiang entered the keywords allergy, asthma, cough and night-time wheezing into an AI tool, which quickly returned a diagnosis of an acute bronchial asthma attack (newspaper account).","causal_attribution":"Guangming Daily's account; the tool is not identified."},{"id":"c2","status":"reported","evidence":[{"locator":"'阳阳妈妈据此拒绝医生建议的胸部X线平片检查，坚持只开雾化药回家'","relation":"supports","source_id":"s1"}],"assertion":"On the basis of that AI diagnosis the mother declined the chest X-ray examination the doctor recommended and insisted on taking home only nebuliser medication.","causal_attribution":"The feature attributes the refusal to the AI diagnosis (据此); this is the newspaper's account."},{"id":"c3","status":"reported","evidence":[{"locator":"'两天后孩子病情加重、呼吸急促，连夜返院检查发现双肺大面积炎症病灶，确诊为偏肺病毒肺炎叠加细菌感染，紧急住院'","relation":"supports","source_id":"s1"}],"assertion":"Two days later the child's condition worsened with rapid breathing; on an overnight return to the hospital, examination found extensive inflammatory lesions in both lungs, and he was diagnosed with human metapneumovirus pneumonia with a superimposed bacterial infection and admitted as an emergency.","causal_attribution":"Clinical course as described in the newspaper feature; it does not say whether pneumonia was present at the first visit."},{"id":"c4","status":"reported","evidence":[{"locator":"'“他们要是早点听我的，病情也不至于这么严重。”浙江省中医院儿科主任李岚无奈地说'","relation":"supports","source_id":"s1"}],"assertion":"The head of paediatrics at Zhejiang Provincial Hospital of Traditional Chinese Medicine is quoted saying the illness would not have become so severe had the family listened earlier.","causal_attribution":"The clinician's assessment that earlier compliance would have limited the severity; the newspaper reports it without an independent review of the records."}],"effects":[{"label":"Three-year-old admitted as an emergency with pneumonia two days after his mother, relying on an AI tool's acute-asthma diagnosis, declined a recommended chest X-ray (newspaper account)","claim_id":"c3","direction":"negative"}],"sources":[{"id":"s1","url":"https://finance.sina.cn/2026-10-08/detail-iniumumr7827547.d.html","kind":"news_article","access":"read","language":"zh","translation_note":"Chinese body read in full on 2026-10-09 and translated by the research agent (an AI). The Sina Finance page republishes a Bingtuan Daily item (兵团日报, dated 10.08 01:37) credited at the end to Guangming Daily (据《光明日报》); the case passage is told in the newspaper's voice and closes with a quotation from the hospital's head of paediatrics; the feature does not say where its account came from. Re-read on 2026-10-11.","independence_group":"guangming-daily-feature"}],"version":1,"ai_roles":["others_use"],"contexts":["health","everyday_life"],"unknowns":["Which AI tool the mother used.","Whether the tool's acute-asthma diagnosis was wrong in itself or only incomplete; the feature describes the later pneumonia diagnosis, not the asthma assessment.","Whether pneumonia was present or detectable at the first visit, when the chest X-ray was declined.","The exact dates in August 2026 of the first visit and the readmission.","The child's course after the emergency admission.","The family's own account, and where the newspaper obtained its account of the case; only the feature's account, closed with the paediatrics head's quotation, is available."],"geography":{"basis":"The feature places the case in Zhejiang (浙江一名3岁男童) and the treating clinician at Zhejiang Provincial Hospital of Traditional Chinese Medicine, so the event and the affected child are in China. No court is involved.","court_countries":[],"event_countries":["CN"],"affected_person_countries":["CN"]},"publication":{"basis":"Published as a concrete account in a national newspaper feature of a parent relying on an AI tool's symptom diagnosis for a young child, declining a recommended chest X-ray, and the child being admitted as an emergency two days later with pneumonia. Every assertion is attributed to the newspaper's account, and the view that the illness would have been less severe had the family listened earlier is attributed to the paediatrics head. The tool is unnamed. The child's pseudonym from the article appears only inside the verbatim Chinese passages of claims c1 and c2 and is not used in the narrative. The worsening and emergency admission after the declined X-ray, rather than the AI's asthma assessment, is recorded as the harm.","reviewed_on":"2026-10-11"},"ai_involvement":{"basis":"The feature states what the AI tool produced: after the mother entered the keywords allergy, asthma, cough and night-time wheezing, it quickly returned the diagnosis acute bronchial asthma attack. It connects that output to the harm in the next sentences: on that basis the mother declined the chest X-ray the doctor recommended and took home only nebuliser medication, and two days later the child was found to have extensive bilateral lung inflammation and was admitted as an emergency with metapneumovirus pneumonia and a bacterial infection. The account is Guangming Daily's, closed with a quotation from the hospital's head of paediatrics; the tool is unnamed and the family's own version is not reported, so the involvement is recorded as reported rather than supported.","status":"reported"},"person_relations":["made_claim_about","informed_decision_about"]},"name":"Zhejiang toddler hospitalised with pneumonia after his mother relied on an AI tool's asthma diagnosis and declined a chest X-ray (newspaper account)","summary":"A Guangming Daily feature on AI symptom-checking, republished by Bingtuan Daily on Sina Finance on 8 October 2026, recounts a case from August 2026 in Zhejiang and closes it with a quotation from the head of paediatrics at a provincial hospital, who says the family did not heed the doctor's advice. A three-year-old boy with a history of asthma was brought in; his mother had entered keywords such as allergy, asthma, cough and night-time wheezing into an AI tool, which quickly returned a diagnosis of an acute bronchial asthma attack. On that basis, the account says, she declined the chest X-ray the doctor recommended and insisted on taking home only nebuliser medication. Two days later the child's condition worsened with rapid breathing; on an overnight return to the hospital, examination found extensive inflammatory lesions in both lungs, and he was diagnosed with human metapneumovirus pneumonia with a superimposed bacterial infection and admitted as an emergency. The paediatrics head is quoted saying the illness would not have become so severe had the family listened earlier. The AI tool is not named. The case is told in the newspaper's voice, and the feature does not say where its account came from beyond the paediatrics head's quotation; no statement from the family is reported.","incidentDate":"2026-08-01","incidentKind":"single_event","incidentDatePrecision":"month","exposurePattern":"single_interaction","reportedDate":"2026-10-08","aiSystem":"An unnamed AI tool into which, by the account in the Guangming Daily feature, the mother entered symptom keywords and which returned a diagnosis of an acute bronchial asthma attack","aiProduct":"Unidentified symptom-analysis tool","severity":"medium","verificationStatus":"unverified","harmCategories":[],"harmOutcomes":["medical_deterioration","hospitalization","treatment_disruption"],"harmOutcomeSummary":"By the newspaper's account, after his mother, relying on an AI tool's acute-asthma diagnosis, declined the chest X-ray a doctor advised, a three-year-old's condition worsened over two days and he was admitted as an emergency with metapneumovirus pneumonia and a bacterial infection; the paediatrics head is quoted saying the illness would not have become so severe had the family listened earlier.","frameworkFacets":[],"causationStatus":"alleged","participantUsersAffectedMin":0,"otherPeopleHarmedMin":1,"affectedCountStatus":"exact","affectedCountEvidence":"One child is reported harmed. The mother used the AI tool; the harm fell on the child, so he is counted as another person harmed and no direct user is counted as harmed.","victimAgeRange":"minor","jurisdiction":"CN","platformType":"other","outcomeStatus":"unknown","primarySourceUrl":"https://finance.sina.cn/2026-10-08/detail-iniumumr7827547.d.html","primarySourceLabel":"Sina Finance (Bingtuan Daily, credited to Guangming Daily), AI热潮下医患问诊之变与辨, 8 October 2026","firstPublishedAt":"2026-10-09T03:36:33.441089+00:00","updatedAt":"2026-10-11T07:43:54.606673+00:00","scopeVersion":"facts-v3","tags":["health","symptom_checker","children","declined_examination","china"]},{"id":"2026-meta-instagram-ai-assisted-account-recovery-tool-exploited-to-reset-passwords","caseFacts":{"claims":[{"id":"c1","status":"corroborated","evidence":[{"locator":"the system incorrectly sent a password reset link to that unassociated email rather than rejecting the request","relation":"supports","source_id":"s1"},{"locator":"This allowed unauthorized third parties to receive a password reset link for accounts they did not own","relation":"supports","source_id":"s1"},{"locator":"The chatbot can be seen sending a verification code to the email address provided by the hacker","relation":"supports","source_id":"s3"},{"locator":"TechCrunch was able to verify that the hacker’s public email mailbox, which was displayed in the video, effectively received the verification code.","relation":"supports","source_id":"s3"}],"assertion":"Through Meta's AI-assisted account recovery support system (High Touch Support), third parties received password reset links or verification codes for Instagram accounts they did not own, sent to an email address that was not associated with the account.","causal_attribution":"Two evidential bases: Meta's own notice to the Maine Attorney General (a party's account of its own system) and videos the attackers posted, in which TechCrunch confirmed that the mailbox shown received the verification code. TechCrunch's check covers that one delivery. It did not test which Meta tool sent the code or who owned the target account, and the videos were not opened for this review. The link between the chat assistant in the videos and High Touch Support is made by press reports and by Meta's spokesperson referring to the AI agent. No inspected document names both. Meta says the tool worked as intended and the failure lay in a separate code path (see c5), so the AI component's own contribution is disputed."},{"id":"c2","status":"reported","evidence":[{"locator":"the hacker opened a chat with Meta AI Support Assistant and asked the bot to add a new email address to the target’s account.","relation":"supports","source_id":"s3"},{"locator":"which prompts the chatbot to show a button to “Reset Password.”","relation":"supports","source_id":"s3"},{"locator":"One video shows a hacker starting a conversation with Meta’s AI support bot and asking it to link the target account with a new email address","relation":"supports","source_id":"s5"},{"locator":"using a VPN connection with an IP address that is in or near the target’s usual hometown","relation":"supports","source_id":"s6"},{"locator":"The bot followed through with the request - sending a code to the hacker's email which, when verified, was followed by an email with a link to change their password.","relation":"supports","source_id":"s7"}],"assertion":"Attackers asked Meta's AI support assistant in a chat to add or link a new email address to a target Instagram username, and some used a VPN to appear in the target's location. In one video the assistant then sent a verification code to that address and showed a button to reset the password.","causal_attribution":"Every account of the chat steps traces to videos and screenshots the attackers posted on Telegram and X. TechCrunch checked one displayed mailbox. The other videos were not independently reproduced."},{"id":"c3","status":"reported","evidence":[{"locator":"the unauthorized party was able to log in to the account if the account holder had not enabled two-factor authentication (2FA)","relation":"supports","source_id":"s1"},{"locator":"The hackers who released the video on Telegram said their exploit failed to work against any accounts that had MFA enabled.","relation":"supports","source_id":"s6"}],"assertion":"Meta's notice says the account could be logged into after the password reset if the account holder had not enabled two-factor authentication. Krebs on Security reports that the attackers who posted the video said the exploit failed against accounts with multi-factor authentication.","causal_attribution":"Meta's statement about its own system and the attackers' own statement as relayed by Krebs. Neither was tested independently."},{"id":"c4","status":"reported","evidence":[{"locator":"it can also take action for you on a growing set of requests directly within Facebook and in the future, on Instagram, including:","relation":"supports","source_id":"s12"},{"locator":"Resetting passwords","relation":"supports","source_id":"s12"},{"locator":"We’ve also started rolling out the support assistant to people who need help logging into their Facebook and Instagram accounts, starting with select cases in the US and Canada","relation":"supports","source_id":"s12"}],"assertion":"Meta announced the Meta AI support assistant for Facebook and Instagram on 19 March 2026, described it as able to take action on requests including resetting passwords directly within Facebook and, in the future, on Instagram, and said it had started rolling it out to people who need help logging into Facebook and Instagram accounts, starting with select cases in the US and Canada.","causal_attribution":"Meta's own product announcement. The announcement does not say which tool the exploited flow used. The link between this assistant and the High Touch Support tool named in Meta's notice is made by the press reports and by the notice's own description of an AI-assisted account recovery system."},{"id":"c5","status":"disputed","evidence":[{"locator":"The tool itself worked properly and functioned as intended; however due to a bug in a separate code path, the system did not properly verify that the email address provided by the individual requesting a password reset matched the email address associated with that user’s Instagram account.","relation":"supports","source_id":"s1"},{"locator":"Some of our internal backend checks failed in this instance, but it wasn’t due to the AI agent itself, and we’ve addressed the underlying cause.","relation":"supports","source_id":"s11"},{"locator":"Hackers simply told Meta’s AI chatbot that they were the owners of the target’s account, and asked the bot to link that person’s account to an email they controlled. The chatbot complied with the request","relation":"contradicts","source_id":"s4"}],"assertion":"Whether the failure lay in the AI agent or in a separate code path is disputed. Meta's notice says the tool worked as intended and that a bug in a separate code path did not check the requester's email address against the account, and a Meta spokesperson told Gizmodo that some internal backend checks failed and that this was not due to the AI agent itself. TechCrunch describes the chatbot as complying with the attackers' request.","causal_attribution":"Meta's account of its own system. TechCrunch's description of the chatbot as complying with the request is a reporter's characterisation from the attackers' videos and does not test where in Meta's system the check failed."},{"id":"c6","status":"reported","evidence":[{"locator":"Date(s) Breach Occured: 04/17/2026","relation":"supports","source_id":"s2"},{"locator":"Date Breach Discovered: 05-31-2026","relation":"supports","source_id":"s2"},{"locator":"May 31, 2026, Meta discovered that there was a vulnerability in an AI-assisted account","relation":"supports","source_id":"s1"},{"locator":"same day the exploitation was identified by Meta, the following actions were taken to","relation":"supports","source_id":"s1"},{"locator":"the AI-assisted support tool removing the vulnerable code path from production","relation":"supports","source_id":"s1"}],"assertion":"Meta's notice lists 17 April 2026 as the date the breach occurred (as 04/17/2026) and 31 May 2026 as the date it discovered the vulnerability, and says Meta disabled the AI-assisted support tool on the same day the exploitation was identified.","causal_attribution":"Meta's own dates for its own system. The notice letter gives the discovery date and no start date. The 17 April date appears only in the listing form, and the basis for it is not stated."},{"id":"c7","status":"reported","evidence":[{"locator":"Total number of persons affected (including residents): 20225","relation":"supports","source_id":"s2"},{"locator":"Total number of Maine residents affected: 30","relation":"supports","source_id":"s2"},{"locator":"reset through the support tool, did not have 2FA enabled on their account and whose Instagram accounts were likely accessed by an unauthorized party.","relation":"supports","source_id":"s1"},{"locator":"This number represents an upper bound of the users impacted as some of the accounts may have been accessed legitimately by account owners.","relation":"supports","source_id":"s1"}],"assertion":"The Maine Attorney General listing of Meta's submission gives 20225 as the total number of persons affected and 30 as the number of Maine residents. The notice defines the Maine figure as users whose passwords were reset through the tool, who had no two-factor authentication and whose accounts were likely accessed by an unauthorized party, and calls it an upper bound because some accounts may have been accessed legitimately by their owners.","causal_attribution":"Meta's own estimate. The notice's upper-bound wording is written for the Maine figure. The inspected notice does not say whether the total of 20225 counts accounts or people, how many were taken over, or how many are organisational accounts."},{"id":"c8","status":"reported","evidence":[{"locator":"“The password got changed without my knowledge and I was getting different password reset attempts throughout yesterday,” said Wong.","relation":"supports","source_id":"s3"},{"locator":"And I got repeatedly logged out from the IG iOS app[.] Quite concerning.","relation":"supports","source_id":"s10"},{"locator":"it took about five to 10 minutes to reinstate her account","relation":"supports","source_id":"s9"},{"locator":"Wong, who previously worked at Meta as a security engineer, said in a post on X her Instagram password was \"changed without my knowledge\"","relation":"supports","source_id":"s7"}],"assertion":"Jane Manchun Wong, a security researcher and former Meta employee, posted on X that her Instagram password was changed without her knowledge, that she received password reset attempts and was repeatedly logged out of the app, and told Reuters that reinstating her account took about five to ten minutes.","causal_attribution":"Her own public statements, relayed by four outlets. The X post itself was not opened. Wong does not say in the quoted statements how her account was accessed, and the outlets connect it to the exploit."},{"id":"c9","status":"reported","evidence":[{"locator":"and the account of the U.S. Space Force’s chief master sergeant","relation":"supports","source_id":"s4"},{"locator":"the account of the U.S. Space Force’s chief master sergeant","relation":"supports","source_id":"s3"},{"locator":"the Chief Master Sergeant of the U.S. Space Force were briefly defaced with pro-Iranian images and messages over the weekend","relation":"supports","source_id":"s6"},{"locator":"the Chief Master Sergeant of Space Force’s account","relation":"supports","source_id":"s5"}],"assertion":"TechCrunch and Krebs on Security report that the Instagram account of the U.S. Space Force's Chief Master Sergeant was compromised, and Krebs reports that it was briefly defaced with pro-Iranian images and messages.","causal_attribution":"Reporters' accounts based on screenshots the attackers posted. The account holder is not quoted in the inspected sources and is described here by office only. Whether the account is a personal or an official office account is not stated."},{"id":"c10","status":"reported","evidence":[{"locator":"including the Barack Obama White House account , the Chief Master Sergeant of Space Force’s account , and Sephora’s account","relation":"supports","source_id":"s5"},{"locator":"The Sephora corporate page and the account belonging to the Chief Master Sergeant of the U.S. Space Force were also hit.","relation":"supports","source_id":"s10"},{"locator":"The Instagram accounts for the Obama White House and the Chief Master Sergeant of the U.S. Space Force were briefly defaced","relation":"supports","source_id":"s6"},{"locator":"The former US president's account reportedly posted pro-Iran content before it was recovered.","relation":"supports","source_id":"s7"},{"locator":"the dormant Obama White House account (which Meta disputed)","relation":"context","source_id":"s4"}],"assertion":"Outlets named the Sephora corporate account and a dormant Obama White House account among the compromised accounts, and Krebs and the BBC report that the Obama White House account was defaced with pro-Iran content. TechCrunch's 3 June report lists the Obama White House account among apparent victims with the parenthetical '(which Meta disputed)'. Both are organisational or institutional accounts and are not counted as affected persons.","causal_attribution":"Reporters' accounts. The Guardian, Gizmodo and Reuters name Sephora on the strength of 404 Media's reporting, so Sephora rests on one chain. TechCrunch does not say what Meta disputed about the Obama White House account. The BBC reports that Meta's spokesperson called claims that world leaders' accounts were hacked totally false."},{"id":"c11","status":"reported","evidence":[{"locator":"allowing the hacker to reset the target account’s password and take control of the account — in some cases locking out the victims.","relation":"supports","source_id":"s4"},{"locator":"locking users out of their accounts and prompting a wave of complaints on platforms including X and Reddit.","relation":"supports","source_id":"s9"},{"locator":"One X user wrote that they had been unable to find \"human support\" after their Instagram account was hacked.","relation":"supports","source_id":"s7"},{"locator":"Everyday users complained of similar hijackings on Reddit and X over the weekend.","relation":"supports","source_id":"s8"}],"assertion":"Some victims were reported locked out of their accounts, and one person wrote on X that they could not find human support after their Instagram account was hacked.","causal_attribution":"Reporters' summaries of complaints on X and Reddit. The individual posts were not opened and the complainants are not identified."},{"id":"c12","status":"reported","evidence":[{"locator":"TechCrunch has seen examples of allegedly hacked handles featuring common forenames or names of countries","relation":"supports","source_id":"s4"},{"locator":"(It’s important to note that it’s hard to know for sure if all these accounts were hacked due to the same technique.)","relation":"supports","source_id":"s4"},{"locator":"hijack a number of valuable (read: short) Instagram account names that allegedly have a resale value of more than a half million dollars.","relation":"supports","source_id":"s6"},{"locator":"404 Media has seen text files of huge lists of “OG,” or high-value, original usernames","relation":"context","source_id":"s5"}],"assertion":"Short Instagram handles were reported taken in the campaign and offered for resale. TechCrunch saw examples of allegedly hacked handles being advertised for sale and notes it is hard to know whether all were taken with this technique. Krebs reports that the attackers claimed the resale value of the short handles they took exceeded half a million dollars.","causal_attribution":"The resale and value claims come from attackers' Telegram posts as relayed by TechCrunch and Krebs. No sale was confirmed and the owners are not identified."},{"id":"c13","status":"reported","evidence":[{"locator":"\"This issue has been resolved and we are securing impacted accounts,\" Meta spokesperson Andy Stone told users in a statement on X","relation":"supports","source_id":"s7"},{"locator":"On Monday, Instagram spokesperson Andy Stone said in a reply to Wong’s post and others that the issue was now fixed.","relation":"supports","source_id":"s3"},{"locator":"Invalidated all existing password reset links that had been generated through the vulnerable path","relation":"supports","source_id":"s1"},{"locator":"potentially affected accounts into a mandatory security checkpoint requiring authentication before any account access","relation":"supports","source_id":"s1"},{"locator":"impacted users to reset their passwords and re-authenticate through secure, verified channels","relation":"supports","source_id":"s1"}],"assertion":"A Meta spokesperson said on X on 1 June 2026 that the issue was resolved and Meta was securing impacted accounts. Meta's notice says that it disabled the tool, invalidated existing password reset links generated through the vulnerable path, enrolled potentially affected accounts in a mandatory security checkpoint and told impacted users to reset their passwords.","causal_attribution":"Meta's statements about its own response. TechCrunch reports that the response did not end the reports (see c14)."},{"id":"c14","status":"reported","evidence":[{"locator":"On Tuesday, however, more Instagram users claimed to have had their accounts hacked.","relation":"supports","source_id":"s4"},{"locator":"who claimed to still be able to exploit Meta’s AI chatbot, and they were advertising apparently hacked handles for sale","relation":"supports","source_id":"s4"}],"assertion":"TechCrunch reported on 3 June 2026 that more Instagram users claimed to have had accounts hacked after Meta said the issue was resolved, and that members of a Telegram channel claimed they could still exploit the chatbot.","causal_attribution":"Claims by users and Telegram members as relayed by TechCrunch. The claims were not verified, and Meta's notice says the tool was disabled on 31 May 2026."}],"effects":[{"label":"A named security researcher reported that her Instagram password was changed without her knowledge and that she was logged out, and she told Reuters the account was reinstated in about five to ten minutes","claim_id":"c8","direction":"negative"},{"label":"The Instagram account of the U.S. Space Force's Chief Master Sergeant was reported compromised and briefly defaced with pro-Iranian content","claim_id":"c9","direction":"negative"},{"label":"Some account holders were reported locked out of their Instagram accounts, and one reported being unable to reach human support","claim_id":"c11","direction":"negative"},{"label":"Short Instagram handles were reported taken and offered for resale on Telegram","claim_id":"c12","direction":"negative"}],"sources":[{"id":"s1","url":"https://www.maine.gov/cgi-bin/agviewerad/ret?loc=4169","kind":"regulatory_filing","access":"read","language":"en","translation_note":"Notice PDF read directly. Its text layer separates words with U+200B characters and detaches the first letter of some paragraphs, so locators from this source are given with those characters read as spaces.","independence_group":"meta-own-statements"},{"id":"s2","url":"https://web.archive.org/web/20260609035813id_/https://www.maine.gov/agviewer/content/ag/985235c7-cb95-4be2-8792-a1252b4f8318/686120c8-63be-4e3c-b7ed-466d65b672f5.html","kind":"official_record","access":"read","language":"en","translation_note":"","independence_group":"meta-own-statements"},{"id":"s3","url":"https://techcrunch.com/2026/06/01/hackers-hijacked-instagram-accounts-by-tricking-meta-ai-support-chatbot-into-granting-access/","kind":"news_report","access":"read","language":"en","translation_note":"","independence_group":"attacker-posted-videos"},{"id":"s4","url":"https://techcrunch.com/2026/06/03/instagram-is-alerting-users-who-were-targeted-by-hackers-during-ai-chatbot-attacks/","kind":"news_report","access":"read","language":"en","translation_note":"","independence_group":"attacker-posted-videos"},{"id":"s5","url":"https://www.404media.co/hackers-simply-asked-meta-ai-to-give-them-access-to-high-profile-instagram-accounts-it-worked/","kind":"news_report","access":"read","language":"en","translation_note":"Read through an Internet Archive capture of 1 June 2026 (20260601172133) because the live page is paywalled. The capture carries the full article.","independence_group":"attacker-posted-videos"},{"id":"s6","url":"https://krebsonsecurity.com/2026/06/hackers-used-metas-ai-support-bot-to-seize-instagram-accounts/","kind":"news_report","access":"read","language":"en","translation_note":"","independence_group":"attacker-posted-videos"},{"id":"s7","url":"https://www.bbc.com/news/articles/c98rzr72dpyo","kind":"news_report","access":"read","language":"en","translation_note":"","independence_group":"attacker-posted-videos"},{"id":"s8","url":"https://www.theguardian.com/technology/2026/jun/01/meta-ai-hack-obama-sephora-instagram","kind":"news_report","access":"read","language":"en","translation_note":"","independence_group":"attacker-posted-videos"},{"id":"s9","url":"https://insideretail.us/how-the-sephora-instagram-hack-exposed-metas-ai-weakness/","kind":"wire_report","access":"read","language":"en","translation_note":"","independence_group":"attacker-posted-videos"},{"id":"s10","url":"https://gizmodo.com/hackers-tricked-meta-ai-into-handing-out-access-to-major-instagram-accounts-2000766087","kind":"news_report","access":"read","language":"en","translation_note":"","independence_group":"attacker-posted-videos"},{"id":"s11","url":"https://gizmodo.com/meta-says-thousands-of-instagram-accounts-were-breached-through-its-ai-support-assistant-2000768770","kind":"news_report","access":"read","language":"en","translation_note":"","independence_group":"meta-own-statements"},{"id":"s12","url":"https://about.fb.com/news/2026/03/boosting-your-support-and-safety-on-metas-apps-with-ai/","kind":"official_statement","access":"read","language":"en","translation_note":"","independence_group":"meta-own-statements"}],"version":1,"ai_roles":["others_use","institutional_use"],"contexts":["privacy","everyday_life"],"unknowns":["How many people or organisations lost control of an account is not established. Meta's listing gives 20225 persons affected and the notice calls the Maine figure an upper bound, and the notice does not say how many accounts were organisational or how many were taken over.","Meta says it is unaware of what, if any, personal information was accessed. Whether any messages or data were read is unknown.","The start date rests on Meta's listing (17 April 2026), and the notice does not state its basis. 404 Media quotes a Telegram channel documenting the hack saying the exploits were 'getting abused after quietly working for months', and separately says that the same account originally posted in Telegram about the vulnerability 'at the end of March' (the year is not stated). Neither statement gives a start date for exploitation. Meta's announcement of 19 March 2026 says the support assistant was previewed 'in December' (year not stated in the passage) and that help with logging in was starting in select cases in the US and Canada, so no inspected source establishes the earliest date of exploitation.","The end date is Meta's date for disabling the tool (31 May 2026). TechCrunch reported unverified claims of continued exploitation on 3 June 2026.","The X posts, the Telegram videos and the Reddit complaints were not opened. Reporters' descriptions of them are used.","The notice does not say how many accounts were restored to their owners, and the listing shows 19 June 2026 as the date of consumer notification in a capture taken on 9 June 2026.","Figures of about 34,000 accounts targeted and a SimpliSafe account appeared only on an aggregator page that attributes the first figure to Meta without a citation and are not used."],"geography":{"basis":"Meta's notice to the Maine Attorney General counts 30 Maine users among those potentially impacted. The countries of the other affected people, the attackers (who reportedly used VPNs to appear in the target's location) and Meta's systems are not stated in the inspected sources, and the country of the named security researcher is not stated.","court_countries":[],"event_countries":[],"affected_person_countries":["US"]},"publication":{"basis":"Meta's notice to the Maine Attorney General (a PDF read directly) and the Maine listing (an archived capture) document Meta's own account of the exploited AI-assisted tool, the dates and the affected count. Nine news reports and Meta's March announcement were read in full. The mechanism claim has two independent chains (Meta's filing and attacker-posted videos checked by TechCrunch). Harm to named account holders rests on their own statements or on reporters relaying attacker-posted screenshots, so those claims stay at reported status. Only one account holder who spoke publicly is named. The office holder is described by office only.","reviewed_on":"2026-09-29"},"ai_involvement":{"basis":"Meta's notice to the Maine Attorney General describes the affected system as an AI-assisted account recovery system (High Touch Support) and says it sent a password reset link to an email address not associated with the account. TechCrunch reports that no Meta employee or contractor took part in the exploit chats and checked one attacker mailbox for the code. Meta says the tool worked as intended, that the failure was a bug in a separate code path that did not verify the email address, and (to Gizmodo) that the failure was not due to the AI agent itself. Whether the AI component or the separate code path caused the failure is disputed and was not tested.","status":"supported"},"person_relations":["made_decision_about"]},"name":"Third parties exploit Meta's AI-assisted Instagram account recovery tool to reset passwords, with account takeovers reported (17 April to 31 May 2026)","summary":"Meta announced the rollout of its AI support assistant on Facebook and Instagram on 19 March 2026. Meta's filing with the Maine Attorney General (notice dated 5 June 2026) says unauthorized third parties exploited a vulnerability in its AI-assisted Instagram account recovery tool (High Touch Support) to receive password reset links for accounts they did not own, and the listing gives 17 April 2026 as the breach date and 31 May 2026 as the discovery date. Videos that attackers posted, as described by TechCrunch, 404 Media and Krebs on Security, show attackers asking the assistant in a chat to link a new email address to a target username. Reported victims include the security researcher Jane Manchun Wong, who posted that her password was changed without her knowledge, the Instagram account of the U.S. Space Force's Chief Master Sergeant, and the accounts of Sephora and a dormant Obama White House page (TechCrunch marks the last as disputed by Meta). Krebs and the BBC report pro-Iran defacement of some accounts, and TechCrunch reports that some victims were locked out and that short handles were offered for resale. The filing gives 20225 persons affected in total and 30 in Maine, and the notice calls the Maine figure an upper bound. Meta says the tool worked as intended, that a bug in a separate code path failed to check the email address, and (through a spokesperson to Gizmodo) that the failure was not due to the AI agent itself. Meta says it disabled the tool on 31 May 2026, the day it discovered the exploitation.","incidentDate":"2026-04-17","incidentEndDate":"2026-05-31","incidentKind":"bounded_series","incidentDatePrecision":"range","exposurePattern":"unknown","reportedDate":"2026-06-01","aiSystem":"Meta AI support assistant / High Touch Support (AI-assisted Instagram account recovery tool)","aiProduct":"Meta AI support assistant","aiCompany":"Meta","severity":"low","verificationStatus":"credible","harmCategories":[],"harmOutcomes":["other_material_harm","reputational_harm"],"harmOutcomeSummary":"Reporters and Meta's notice report that third parties reset passwords on Instagram accounts and, where the account had no two-factor authentication, could log in. A named security researcher reports her password was changed without her knowledge and that reinstating the account took about five to ten minutes. Krebs on Security and the BBC report that some high-profile accounts were briefly defaced, TechCrunch reports that some victims were locked out and that short handles were offered for resale, and Meta says it does not know what personal information, if any, was accessed. Meta's filing gives 20225 persons affected in total, and its notice calls the Maine figure an upper bound.","frameworkFacets":[],"causationStatus":"disputed","participantUsersAffectedMin":0,"otherPeopleHarmedMin":2,"affectedCountStatus":"partial","affectedCountEvidence":"Two account holders are counted: the security researcher who posted that her account was taken over, and the office holder whose Instagram account TechCrunch and Krebs on Security report as compromised. TechCrunch's 3 June article says this account 'appeared to be' among the victims, no statement from the office holder or from Meta about this account was inspected, and whether it is a personal or an official account is not stated. Sephora and the Obama White House account are organisational or institutional accounts and are not counted. Other victims (everyday users, short-handle holders) are unquantified. Meta's listing of 20225 persons affected is not counted: the notice calls the Maine figure an upper bound and does not say how many accounts were taken over or how many were organisational.","victimAgeRange":"unknown","platformType":"assistant","primarySourceUrl":"https://www.maine.gov/cgi-bin/agviewerad/ret?loc=4169","primarySourceLabel":"Meta incident notification to the Maine Attorney General (5 June 2026)","firstPublishedAt":"2026-09-29T21:16:54.181323+00:00","updatedAt":"2026-09-30T01:17:45.477765+00:00","scopeVersion":"facts-v3","tags":["historical-2026"]},{"id":"2026-south-africa-sassa-elife-certification-portal-facial-verification-failures-reported-by-pensioners","caseFacts":{"claims":[{"id":"c1","status":"reported","evidence":[{"locator":"The eLife Certification was implemented on March 30, 2026, as a digital verification tool to curb fraud.","relation":"supports","source_id":"s1"},{"locator":"Beneficiaries who fail to complete the process risk having their grants suspended.","relation":"supports","source_id":"s1"},{"locator":"secure biometric verification through the electronic Know Your Client (eKYC) system","relation":"supports","source_id":"s2"},{"locator":"Beneficiaries who fail to complete life certification as directed may face payment delays or suspension of their grants.","relation":"supports","source_id":"s2"}],"assertion":"SASSA's eLife Certification is a self-service life certification on its online portal that uses biometric verification through its electronic Know Your Client (eKYC) system. IOL reports it was implemented on 30 March 2026. SASSA said beneficiaries who fail to complete life certification as directed may face payment delays or suspension of their grants.","causal_attribution":"The implementation date comes from IOL alone. SASSA statements read do not give a start date. The suspension consequence is SASSA's own stated rule and no suspension of either pensioner's grant is reported."},{"id":"c2","status":"reported","evidence":[{"locator":"SASSA would like to apologise to all our beneficiaries who could not access our self-service portal after they were notified to undertake the eLife Certification verification process by the Agency.","relation":"supports","source_id":"s2"},{"locator":"there were system glitches which led to delay and disruptions in completing eLife Certification, leading to long queues at SASSA offices.","relation":"supports","source_id":"s2"},{"locator":"the Agency can report that the challenge has been resolved.","relation":"supports","source_id":"s2"}],"assertion":"On 10 April 2026 SASSA apologised to beneficiaries who could not access its self-service portal after being notified to complete eLife Certification. It said system glitches linked to interfaces with other departments had caused delays and disruptions and long queues at its offices, and said the challenge had been resolved.","causal_attribution":"SASSA's own account of its portal. The statement does not mention facial recognition and attributes the glitches to interfaces with other departments."},{"id":"c3","status":"reported","evidence":[{"locator":"both pensioners, told IOL they had tried to complete the facial recognition option on the portal but to no avail.","relation":"supports","source_id":"s1"},{"locator":"We have been trying since Thursday, April 2, to do the selfie bit but it does not work after trying for 22 times","relation":"supports","source_id":"s1"}],"assertion":"A pensioner couple told IOL they had tried the facial recognition option on the eLife portal 22 times since 2 April 2026 without success. IOL published the account on 23 April 2026.","causal_attribution":"Single first-person account relayed by one outlet. The cause of the failures is not established. The department attributes facial verification problems in general to poor lighting, unstable connectivity or missing Home Affairs biometric records (see c6)."},{"id":"c4","status":"reported","evidence":[{"locator":"IOL has been inundated with emails and calls from beneficiaries nationwide claiming they were unable to complete the mandatory certification process.","relation":"supports","source_id":"s1"},{"locator":"beneficiaries cite consistent failures with facial recognition and one-time pins (OTPs).","relation":"supports","source_id":"s1"},{"locator":"The system just kept on loading and never went through to my profile. I have been struggling for three weeks","relation":"supports","source_id":"s1"},{"locator":"Then also indicated that the Department of Home Affairs is not available to verify my particulars","relation":"supports","source_id":"s1"}],"assertion":"IOL reported that beneficiaries nationwide contacted it to say they could not complete the certification and cited failures with facial recognition and one-time PINs. One pensioner said the site kept loading without reaching their profile for three weeks, and reported a one-time PIN rejection and a message that Home Affairs was not available to verify their particulars.","causal_attribution":"Unquantified accounts relayed by IOL. The pensioner who described the loading failure and the one-time PIN rejection did not describe a facial recognition failure."},{"id":"c5","status":"reported","evidence":[{"locator":"The Sassa portals are working as evidenced by the number of clients who have accessed the online services.","relation":"supports","source_id":"s1"},{"locator":"As of April 16, 2026, 13,644 (88%) of the 15,499 unique clients who accessed the online verification services via the client portal were successfully verified","relation":"supports","source_id":"s1"},{"locator":"However, Sassa admitted the system has been working intermittently.","relation":"supports","source_id":"s1"}],"assertion":"A SASSA spokesperson told IOL the portals are working and that, as of 16 April 2026, 13,644 (88%) of 15,499 unique clients who accessed the online verification services via the client portal were successfully verified. IOL reports SASSA admitted the system had been working intermittently.","causal_attribution":"SASSA's own figures and account, which were not independently verified. The figures count clients who accessed online verification and do not report how many failed the facial step."},{"id":"c6","status":"reported","evidence":[{"locator":"SASSA said most non-verification cases were driven by beneficiaries failing to respond to notifications, not completing life certification, or unsuccessful facial recognition attempts on online platforms.","relation":"supports","source_id":"s3"},{"locator":"In such cases, beneficiaries are redirected to fingerprint biometric verification at local offices.","relation":"supports","source_id":"s3"},{"locator":"The agency said it had recorded 7,779 complaints linked to its electronic facial biometric system","relation":"supports","source_id":"s3"},{"locator":"The department attributed facial verification issues to poor lighting, unstable connectivity, or missing biometric records at the Department of Home Affairs.","relation":"supports","source_id":"s3"},{"locator":"The agency said it had recorded 7 779 complaints linked to its electronic facial biometric system.","relation":"supports","source_id":"s4"}],"assertion":"IOL's 24 May 2026 report on a parliamentary reply says SASSA said most non-verification cases were driven by beneficiaries who did not respond to notifications, did not complete life certification, or had unsuccessful facial recognition attempts on online platforms, and that such beneficiaries are redirected to fingerprint verification at local offices. IOL says SASSA had recorded 7,779 complaints linked to its electronic facial biometric system and that the department attributed facial verification issues to poor lighting, unstable connectivity or missing biometric records at the Department of Home Affairs.","causal_attribution":"SASSA's account relayed by two outlets that share one reporter and one reply, so they are one chain. The reports do not date the complaints or say whether they concern eLife Certification or earlier online facial verification, and do not say how many were repeat complaints."},{"id":"c7","status":"reported","evidence":[{"locator":"with 67,868 grants suspended in the third quarter alone","relation":"supports","source_id":"s3"},{"locator":"a grant is suspended 2 months after a beneficiary was notified to conduct a review and has not yet done so","relation":"supports","source_id":"s3"},{"locator":"around 70 000 grants have been suspended due to beneficiaries failing to come forward for review","relation":"supports","source_id":"s5"}],"assertion":"The parliamentary reply reported 67,868 grants suspended in the third quarter (the reports do not identify the period) under a rule that a grant is suspended two months after a beneficiary was notified to conduct a review and has not yet done so. A Parliament committee statement of 5 February 2026 reported around 70,000 grants suspended for beneficiaries failing to come forward for review.","causal_attribution":"The suspension figures are context. No inspected report says how many suspensions followed a facial verification failure, and the committee statement predates the eLife implementation date reported by IOL."}],"effects":[{"label":"Pensioners reported repeated failures of the facial recognition step in a mandatory online life certification, with a stated risk of payment delay or grant suspension if it is not completed","claim_id":"c3","direction":"negative"},{"label":"SASSA reported delays, disruptions and long queues at its offices after beneficiaries could not use the self-service certification portal, which SASSA attributed to interfaces with other departments (its statement does not mention facial recognition)","claim_id":"c2","direction":"negative"}],"sources":[{"id":"s1","url":"https://iol.co.za/news/south-africa/2026-04-23-sassa-elife-certification-portal-beneficiaries-report-ongoing-glitches-despite-agency-denials/","kind":"news_report","access":"read","language":"en","translation_note":"","independence_group":"iol-elife-glitches-report"},{"id":"s2","url":"https://www.gov.za/news/media-statements/sassa-self-service-system-restored-following-earlier-challenges-10-apr-2026","kind":"official_statement","access":"read","language":"en","translation_note":"","independence_group":"sassa-10-apr-2026-statement"},{"id":"s3","url":"https://iol.co.za/news/south-africa/2026-05-24-sassas-biometric-rollout-leaves-thousands-without-grants-amid-fraud-crackdown/","kind":"news_report","access":"read","language":"en","translation_note":"","independence_group":"parliamentary-reply-iol-report"},{"id":"s4","url":"https://dailyvoice.co.za/news/2026-05-25-sassas-face-palm-facial-recognition-tech-linked-to-the-suspension-of-68-000-grants/","kind":"news_report","access":"read","language":"en","translation_note":"","independence_group":"parliamentary-reply-iol-report"},{"id":"s5","url":"https://www.parliament.gov.za/index.php/press-releases/media-statement-committee-notes-grant-reviews-are-necessary-protect-poor-and-public-funds","kind":"official_statement","access":"read","language":"en","translation_note":"","independence_group":"parliament-committee-5-feb-2026-statement"}],"version":1,"ai_roles":["institutional_use"],"contexts":["public_services","accessibility"],"unknowns":["The reports do not say how many of the 67,868 grant suspensions (third quarter, period not identified) followed unsuccessful facial recognition. The suspensions are governed by a review non-response rule, and a committee statement dated 5 February 2026 already reported around 70,000 suspensions before the eLife implementation date reported by IOL.","The 30 March 2026 implementation date comes from IOL only. The SASSA statements read do not give a start date.","SASSA's statement refers to facial recognition on online platforms in general. Neither IOL 24 May 2026 nor Daily Voice 25 May 2026 mentions eLife Certification, and IOL places the reply within a biometric verification rollout dated from September 2025 (compulsory biometric enrolment for new applicants, verified at local offices). Whether the 7,779 complaints and the redirections to fingerprint checks concern eLife Certification at all is not stated. Facial photo verification through the same eKYC system for Social Relief of Distress grant applicants was reported earlier (Biometric Update, August 2024, and Corruption Watch, January 2025) and is a separate earlier deployment that this case does not cover.","Whether the pensioner couple later completed certification, or whether any grant was delayed or suspended, is not reported.","The cause of the couple's failed attempts is not established (lighting, connectivity, missing Home Affairs records, or the facial matching itself).","SASSA said on 10 April 2026 that the problem was resolved, and IOL reported failures continuing on 23 April 2026. The 88% success figure is SASSA's and was not checked.","The pensioner accounts come from one outlet (IOL). A Joburg ETC article of the same date relays it and adds nothing independent.","IOL page dates were taken from the URLs (23 April and 24 May 2026) because the page bodies show only relative ages."],"geography":{"basis":"IOL reports social grant recipients across South Africa struggling with the portal, and the SASSA statement and parliamentary reply concern the South African Social Security Agency's beneficiaries.","court_countries":[],"event_countries":["ZA"],"affected_person_countries":["ZA"]},"publication":{"basis":"IOL (23 April and 24 May 2026), SASSA's 10 April 2026 statement on gov.za, Daily Voice and a Parliament committee statement were read in full. SASSA's and IOL's accounts are attributed and left at reported, and the pensioners' failures come from one outlet. The pensioners are not named. No inspected report attributes any grant suspension to facial verification failures.","reviewed_on":"2026-09-29"},"ai_involvement":{"basis":"The sources describe a facial recognition step in SASSA's eLife Certification portal, which uses biometric verification through the eKYC system and integration with Home Affairs systems, and IOL's 24 May 2026 report of a parliamentary reply refers to SASSA's electronic facial biometric system without saying whether it is the eLife portal. The vendor and model are not identified. The department attributes facial verification problems to poor lighting, unstable connectivity or missing Home Affairs biometric records, and a SASSA spokesperson says the portals work with intermittent downtime, so the cause of any individual failure is not established.","status":"reported"},"person_relations":["made_decision_about"]},"name":"South Africa: pensioners report repeated failures of the facial recognition step in SASSA's eLife certification portal, and SASSA reports disruptions and office queues","summary":"The South African Social Security Agency (SASSA) introduced an online eLife Certification (life certification) for grant beneficiaries that uses biometric verification through its electronic Know Your Client (eKYC) system. IOL reports the certification was implemented on 30 March 2026. SASSA says beneficiaries who do not complete life certification as directed may face payment delays or suspension. On 10 April 2026 SASSA apologised to beneficiaries who could not access the portal, said system glitches linked to interfaces with other departments had caused delays, disruptions and long queues at its offices, and said the problem was resolved. On 23 April 2026 IOL reported that a pensioner couple said they had tried the facial recognition option 22 times since 2 April without success, and that beneficiaries nationwide told IOL they could not complete the certification, citing failures with facial recognition and one-time PINs, with one pensioner also reporting a message that Home Affairs was not available to verify their particulars. A SASSA spokesperson said the portals work and that 13,644 (88%) of the 15,499 unique clients who accessed the online verification services by 16 April were verified, and IOL reports SASSA admitted the system has been working intermittently. In a May 2026 report on a parliamentary reply, IOL said SASSA stated that unsuccessful facial recognition attempts on online platforms were among the causes of non-verification (those beneficiaries are redirected to fingerprint checks at local offices) and that it had recorded 7,779 complaints linked to its electronic facial biometric system. The department attributed facial verification issues to poor lighting, unstable connectivity or missing biometric records at Home Affairs. Neither May report mentions the eLife portal, and IOL places the figures within a biometric verification rollout that it dates from September 2025. The reports do not say how many grants were suspended because of facial verification failures.","incidentDate":"2026-03-30","incidentKind":"bounded_series","incidentDatePrecision":"day","exposurePattern":"repeated_interactions","reportedDate":"2026-04-23","aiSystem":"Facial recognition step in SASSA's eLife Certification portal (biometric verification through the eKYC system, integrated with Home Affairs systems). Vendor and model not identified in the sources.","aiProduct":"SASSA eLife facial verification","aiCompany":"South African Social Security Agency (SASSA), deployer","severity":"low","verificationStatus":"unverified","harmCategories":[],"harmOutcomes":["other_material_harm"],"harmOutcomeSummary":"SASSA said glitches caused delays, disruptions and long queues at its offices, and a pensioner couple told IOL they had tried the facial recognition step 22 times since 2 April without success. SASSA warned that beneficiaries who do not complete life certification as directed may face payment delays or suspension. No inspected report says that either pensioner's grant was delayed or suspended.","frameworkFacets":[],"causationStatus":"alleged","participantUsersAffectedMin":0,"otherPeopleHarmedMin":2,"affectedCountStatus":"partial","affectedCountEvidence":"IOL reports one pensioner couple (two people) who said the facial recognition step failed 22 times. IOL says it was inundated with emails and calls from beneficiaries nationwide and SASSA recorded 7,779 complaints, but complaints are not people and the number of beneficiaries who failed facial verification is not reported, so no larger count is recorded. The 67,868 grant suspensions are not counted because no inspected report attributes them to facial verification.","victimAgeRange":"adult","platformType":"other","primarySourceUrl":"https://iol.co.za/news/south-africa/2026-04-23-sassa-elife-certification-portal-beneficiaries-report-ongoing-glitches-despite-agency-denials/","primarySourceLabel":"IOL (23 Apr 2026)","firstPublishedAt":"2026-09-29T21:16:13.146866+00:00","updatedAt":"2026-09-30T01:17:54.03839+00:00","scopeVersion":"facts-v3","tags":["historical-2026"]},{"id":"2026-broffoni-google-ai-false-identification","caseFacts":{"claims":[{"id":"c1","status":"reported","evidence":[{"locator":"'Una mujer a la que no conocía le avisó que en varios grupos de WhatsApp de Ceuta estaban circulando videos e imágenes suyas y que se decía que estaba proporcionando gas pimienta a inmigrantes marroquíes'; 'Recibí amenazas de muerte, de violación y ataques en general.'","relation":"supports","source_id":"s1"}],"assertion":"On 26 August 2026, WhatsApp groups in Ceuta circulated videos and images claiming Flavia Broffoni was a woman filmed there allegedly giving pepper spray to Moroccan migrants, and she received death and rape threats.","causal_attribution":"Broffoni's account to La Nación, supported by the warning email and the group screenshot shown to the outlet. One reporting chain; the threats are her report, attributed."},{"id":"c2","status":"reported","evidence":[{"locator":"Screenshot passage: 'uno de los usuarios había tomado un recorte del rostro de la mujer del video y lo había ingresado en una herramienta de inteligencia artificial de Google para consultarle quién era. La consulta incluía como contexto la palabra \"activista\". La respuesta identificaba a la persona de la fotografía como Flavia Broffoni'.","relation":"supports","source_id":"s1"},{"locator":"Google Argentina response: 'no pueden confirmar que la captura corresponda a una respuesta generada por sus sistemas porque no cuentan con un enlace al resultado original'; no formal report received.","relation":"context","source_id":"s1"}],"assertion":"The identification originated from a Google AI answer: a group user cropped the woman's face from the video and queried a Google AI tool with the context word 'activista'; the answer identified her as Flavia Broffoni and described her public profile.","causal_attribution":"The screenshot is the evidence of the AI answer; Google neither confirmed nor denied its provenance. The claim is attributed to the screenshot account, not asserted as independently proven."},{"id":"c3","status":"documented","evidence":[{"locator":"'Este medio también probó utilizar la búsqueda de Google a partir del video de la mujer que filmó en Ceuta, y la respuesta de la IA fue afirmar que se trataba de otra persona, una estudiante y community manager oriunda de Quilmes, de la cual brindó datos personales y redes sociales.'","relation":"supports","source_id":"s1"}],"assertion":"La Nación itself ran the same video through Google's search and the AI asserted the woman was a different person — a student and community manager from Quilmes — and supplied her personal data and social networks.","causal_attribution":"The outlet documents its own replication test — direct evidence that the tool produces false identifications from this input; the second misidentified person is not counted as harmed (no virality-driven harm to her is reported)."},{"id":"c4","status":"reported","evidence":[{"locator":"'Yo estoy en la Patagonia, Argentina y nunca tuve relación con lo que está ocurriendo allá. La última vez que estuve en España, si mal no recuerdo, fue en 2014'; the 'tres mentiras' analysis; the others'-tests passage ('muy probablemente', short brown hair vs her current long grey hair).","relation":"supports","source_id":"s1"}],"assertion":"Broffoni says she is not the woman in the video and was in Patagonia, having last visited Spain in 2014; she also notes there is no evidence the real woman distributed pepper spray, and that tests by other people with the same photo sometimes produced refusals and sometimes 'muy probablemente' her, justified partly from outdated photos.","causal_attribution":"Her account; the factual impossibility is uncontested in the inspected reporting. The real woman in the video is unidentified and the pepper-spray claim about her is unverified."}],"effects":[{"label":"false AI identification attached to an invented accusation, followed by death and rape threats","claim_id":"c2","direction":"negative"}],"sources":[{"id":"s1","url":"https://www.lanacion.com.ar/sociedad/una-ia-identifico-erroneamente-a-una-activista-argentina-en-un-video-de-ceuta-denuncia-hostigamiento-nid28082026/","kind":"news_report","access":"read","language":"es","translation_note":"Read in Spanish on 2026-09-15 (datePublished 2026-08-28T15:09Z; 25 substantive paragraphs including the Broffoni interview, the screenshot account, the outlet's own test and Google Argentina's response). Model translation, no human reviewer.","independence_group":"la-nacion"}],"version":1,"ai_roles":["unknown"],"contexts":["everyday_life","privacy"],"unknowns":["Which Google product produced the identification is not named in the inspected reporting; only 'una herramienta de inteligencia artificial de Google' is described.","Whether a formal complaint or lawsuit was filed after 28 August 2026 is not reported.","The identity of the woman actually filmed in Ceuta, and any basis for the pepper-spray claim about her, is unknown.","The student from Quilmes falsely identified in La Nación's test: whether she experienced any harm from the tool's identification is unreported.","The reach of the false identification beyond the Ceuta WhatsApp groups (views, reshares) is not quantified."],"geography":{"basis":"Event: the identification and its circulation happened in Ceuta — the screenshot came from a Ceuta WhatsApp group and the warning sender is described as a citizen of Ceuta. Affected person: Broffoni is in Epuyén, Chubut, Argentine Patagonia ('Yo estoy en la Patagonia, Argentina'). No court proceeding is reported.","court_countries":[],"event_countries":["ES"],"affected_person_countries":["AR"]},"publication":{"basis":"Published under the 2026-09-15 charter as a consequential false claim about a person (made_claim_about): a named adult publicly pursuing accountability, documented through one strong original chain that includes the outlet's own replication of the failure. Threats are attributed to her account; the AI answer's provenance is attributed to the screenshot account with Google's neither-confirm-nor-deny response recorded.","reviewed_on":"2026-09-15"},"ai_involvement":{"basis":"The WhatsApp-group screenshot shows a Google AI answer naming Broffoni from a face crop with 'activista' context; La Nación independently reproduced a false identification of a different person from the same video; Broffoni reports that tests by others sometimes produced 'muy probablemente' her. Google Argentina neither confirmed nor denied that the screenshot came from its systems, asking for the original link. The specific product is not named in the inspected reporting.","status":"supported"},"person_relations":["made_claim_about"]},"name":"Argentine activist reports threats after an alleged Google AI misidentification","summary":"On 26 August 2026, WhatsApp groups in Ceuta circulated videos and images claiming that Argentine political scientist and activist Flavia Broffoni — who was in Patagonia and had not been to Spain since 2014 — was a woman filmed in Ceuta allegedly giving pepper spray to Moroccan migrants. A screenshot from one group shows that a user cropped the woman's face from the video and asked a Google AI tool who she was, with the word 'activista' as context; the answer identified her as Flavia Broffoni with details of her public profile. Broffoni received death and rape threats. La Nación's own test with the same video produced a different false identification — a student from Quilmes, with her personal data. Google Argentina said it could not confirm the screenshot came from its systems without the original link and had received no formal report. Broffoni is weighing legal action with her lawyer.","incidentDate":"2026-08-26","incidentEndDate":"2026-08-28","incidentKind":"bounded_series","incidentDatePrecision":"range","exposurePattern":"single_interaction","reportedDate":"2026-08-28","aiSystem":"Google AI tool answering a face-crop query (product not named in inspected reporting)","aiProduct":"Unidentified Google AI tool (reported)","aiCompany":"Google","severity":"high","verificationStatus":"credible","harmCategories":[],"harmOutcomes":["psychological_distress","reputational_harm"],"harmOutcomeSummary":"A false AI identification attached to an invented accusation spread in Ceuta WhatsApp groups brought death and rape threats to a woman who was demonstrably on another continent, plus reputational damage she is now addressing with a lawyer.","frameworkFacets":[],"causationStatus":"supported","participantUsersAffectedMin":0,"otherPeopleHarmedMin":1,"affectedCountStatus":"documented_minimum","affectedCountEvidence":"One documented harmed person: Broffoni, named and interviewed. The student from Quilmes falsely identified in La Nación's own test is not counted — no harm to her from virality is reported (the test was the outlet's own); she is recorded in the unknowns.","victimAgeRange":"adult","jurisdiction":"AR","platformType":"assistant","outcomeType":"media_coverage","outcomeStatus":"ongoing","primarySourceUrl":"https://www.lanacion.com.ar/sociedad/una-ia-identifico-erroneamente-a-una-activista-argentina-en-un-video-de-ceuta-denuncia-hostigamiento-nid28082026/","primarySourceLabel":"La Nación (28 Aug 2026, Aldana Rizzuto) — interview with Broffoni, the WhatsApp screenshot account, the outlet's own replication test, and Google Argentina's response","firstPublishedAt":"2026-09-15T09:23:34.062763+00:00","updatedAt":"2026-10-05T11:08:54.009102+00:00","scopeVersion":"facts-v3","tags":["made-claim-about","false-identification","google-ai","argentina","ceuta","threats","defamation-adjacent"]}]}