{"meta":{"exportedAt":"2026-10-05T08:13:12.244Z","formatVersion":2,"selection":{"q":"search","system":"","harm":"","context":"","country":"","role":"","relation":"contextual","evidence":"","year":"2026","response":"","severity":"","verification":"","view":"incidents","sort":"added"},"totalIncidents":6,"coverage":{"cases":6,"countries":3,"languages":3,"unknownLocation":3,"locationPending":0,"unknownLanguage":0,"unknownDate":0,"lawsuits":0,"regulatory":0,"minors":0,"coreRelations":1,"contextualRelations":6,"mixedRelations":1,"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-lexington-kentucky-flock-alpr-vehicle-description-search-police-surround-wrong-home","caseFacts":{"claims":[{"id":"c1","status":"reported","evidence":[{"locator":"'in the early hours of Sept. 26, 2026'; 'officers surrounded his home'; 'The group of police left around 10 minutes later.'","relation":"supports","source_id":"s1"},{"locator":"'one with a gun unholstered'","relation":"supports","source_id":"s2"},{"locator":"'spotlights were shining on the home as officers surrounded it'","relation":"supports","source_id":"s3"}],"assertion":"In the early hours of 26 September 2026 Lexington police officers surrounded a couple's home, with spotlights and at least one officer's gun unholstered, and knocked on the door. Officers told the couple they were not suspects and left.","causal_attribution":"Each outlet reports the resident's doorbell video and its own interview; the three accounts rest on the same residents and video."},{"id":"c2","status":"reported","evidence":[{"locator":"'Due to the time of day there was only one return matching the suspect vehicle, resulting in the response to the residence'","relation":"supports","source_id":"s1"},{"locator":"'did not provide a license plate number. Officers entered that information into the Flock system and found a vehicle they believed matched'","relation":"supports","source_id":"s3"},{"locator":"'officers used the Flock Safety System, which includes 125 automatic license plate reader cameras placed around the city, to follow up on the lead'","relation":"supports","source_id":"s2"}],"assertion":"Police were investigating a reported assault in a road-rage incident. Without a license plate, officers searched the city's Flock camera system using the vehicle description, and the single matching return led them to the couple's home.","causal_attribution":"Lexington police statements to each outlet (one originating party)."},{"id":"c3","status":"reported","evidence":[{"locator":"'further investigation enabled officers to determine the vehicle was not the suspect vehicle in question and the scene was cleared'; 'This was not a misidentification'","relation":"supports","source_id":"s1"},{"locator":"'they determined almost immediately that he was not the suspect they were looking for'","relation":"supports","source_id":"s2"}],"assertion":"Police determined that the couple's truck was not the suspect vehicle and placed no charges in relation to it. The department said this was not a misidentification but a lead that was followed up.","causal_attribution":"Lexington police statements as reported."},{"id":"c4","status":"reported","evidence":[{"locator":"'My grandmother was scared to death'; '94-year-old grandmother inside the home'","relation":"supports","source_id":"s3"},{"locator":"'he’s scared to drive his truck again'","relation":"supports","source_id":"s1"}],"assertion":"The residents said the armed early-morning response frightened them and the resident's 94-year-old grandmother, who was inside the home, and the resident said he was scared to drive his truck again.","causal_attribution":"The residents' own accounts to LEX 18 and WEKU."},{"id":"c5","status":"reported","evidence":[{"locator":"'Officers showed the Flock image of the vehicle to the victim, who confirmed it.'","relation":"supports","source_id":"s3"}],"assertion":"LEX 18 reported that officers showed the Flock image of the truck to the road-rage victim, who said it was the same vehicle, before going to the home.","causal_attribution":"The police commander's account to LEX 18; it places a human identification step between the Flock return and the response."}],"effects":[{"label":"police with at least one gun unholstered surrounded a couple's home at about 4 a.m. after a license-plate camera search by vehicle description returned their truck","claim_id":"c1","direction":"negative"}],"sources":[{"id":"s1","url":"https://www.weku.org/lexington-richmond/2026-09-30/flock-search-that-led-lexington-police-to-surround-wrong-home-intensifies-debate-over-the-tech","kind":"news_report","access":"read","language":"en","translation_note":"Read live in English on 2026-10-05 (WEKU public radio, 30 September 2026). Rests on WEKU's own interview with the resident and a written statement from the Lexington Police Department.","independence_group":"weku-lexington-interview-and-lpd-statement"},{"id":"s2","url":"https://www.wkyt.com/2026/09/28/lexington-couple-questions-police-response-after-flock-camera-lead/","kind":"local_tv_news","access":"read","language":"en","translation_note":"Read live in English on 2026-10-05 (WKYT, 28 September 2026). Rests on WKYT's own interviews with the couple and a Lexington police patrol commander.","independence_group":"wkyt-lexington-interviews"},{"id":"s3","url":"https://www.lex18.com/news/covering-kentucky/lexington-couple-questions-flock-cameras-after-lead-mismatches-their-car-in-road-rage-case","kind":"local_tv_news","access":"read","language":"en","translation_note":"Read live in English on 2026-10-05 (LEX 18 News, article body from the page's structured data; the page's structured data gives datePublished 29 September 2026, updated 30 September). Rests on LEX 18's own interviews with the couple and the same police commander.","independence_group":"lex18-lexington-interviews"}],"version":1,"ai_roles":["institutional_use"],"contexts":["justice"],"unknowns":["How the Flock description search works and how many candidate vehicles it returned before filtering by time.","How officers determined at the door that the truck was not the suspect vehicle.","Whether the couple filed a complaint and whether the department reviewed the response.","Whether the suspect vehicle was later identified."],"geography":{"basis":"Lexington police went to a home in Lexington, Kentucky (WEKU, WKYT, LEX 18).","court_countries":[],"event_countries":["US"],"affected_person_countries":["US"]},"publication":{"basis":"Published under the 2026-09-15 charter as an institutional-use case. Three local outlets, each with its own interviews, report that a Flock search by vehicle description returned one truck and that police then surrounded its owner's home at about 4 a.m. with a gun unholstered, and that police found it was not the suspect vehicle. The police dispute the word misidentification. The residents are named by the outlets and are not named here. Claims are reported because they rest on the same residents and police statements.","reviewed_on":"2026-10-05"},"ai_involvement":{"basis":"The Lexington Police Department told WEKU that officers queried its Flock network with only a vehicle description, that one return matched the suspect vehicle, and that this resulted in the response to the residence. A police commander gave the same account to WKYT and LEX 18. WEKU quotes a mayoral candidate referring to the AI technology that powers the cameras; the department does not describe the technology.","status":"supported"},"person_relations":["made_claim_about"]},"name":"Lexington, Kentucky: police surrounded a couple's home at about 4 a.m. in September 2026, one officer with a gun unholstered, after a Flock camera search by vehicle description returned their truck in a road-rage investigation","summary":"WEKU, WKYT and LEX 18 reported that Lexington police surrounded a couple's home in the early hours of 26 September 2026 while investigating a reported assault in a road-rage incident. The victim had described a dark pickup truck and gave no license plate. The Lexington Police Department said officers searched its Flock camera network using the description, that only one return matched at that time of day, and that this led to the response to the residence. Doorbell video showed several police cars, spotlights and an officer with a gun unholstered at the door. Officers told the couple they were not suspects and left after about ten minutes. Police said they determined the truck was not the suspect vehicle, placed no charges and described the visit as following up a lead, not a misidentification. The residents said the response frightened them and a 94-year-old relative inside the home.","incidentDate":"2026-09-26","incidentKind":"single_event","incidentDatePrecision":"day","exposurePattern":"single_interaction","reportedDate":"2026-09-28","aiSystem":"Flock Safety camera network of 125 automatic license plate readers used by the Lexington Police Department, searched by vehicle description without a plate number (police statements to WEKU, WKYT and LEX 18)","aiProduct":"Flock Safety license plate readers","aiCompany":"Flock Safety","severity":"low","verificationStatus":"credible","harmCategories":[],"harmOutcomes":["psychological_distress"],"harmOutcomeSummary":"The residents told WEKU, WKYT and LEX 18 that the armed response at about 4 a.m. frightened them. The resident told LEX 18 and WEKU that it frightened his 94-year-old grandmother, and told WEKU he was scared to drive his truck again.","frameworkFacets":[],"causationStatus":"supported","participantUsersAffectedMin":0,"otherPeopleHarmedMin":3,"affectedCountStatus":"exact","affectedCountEvidence":"Three people in the home: the resident and fiancee who answered the door, and the resident's 94-year-old grandmother, whom he describes as scared to death (LEX 18; WEKU). Exact 3.","victimAgeRange":"adult","jurisdiction":"US-KY","platformType":"other","outcomeType":"media_coverage","outcomeStatus":"unknown","primarySourceUrl":"https://www.weku.org/lexington-richmond/2026-09-30/flock-search-that-led-lexington-police-to-surround-wrong-home-intensifies-debate-over-the-tech","primarySourceLabel":"WEKU, 30 September 2026: Flock search that led Lexington police to surround wrong home intensifies debate over the tech","firstPublishedAt":"2026-10-05T03:12:42.544438+00:00","updatedAt":"2026-10-05T03:12:42.544438+00:00","scopeVersion":"facts-v3","tags":["flock","alpr","license-plate-reader","vehicle-description-search","wrong-home","kentucky","lexington","justice","made-claim-about"]},{"id":"2026-turnitin-ai-checker-marks-ap-research-student-annotations-100-percent-ai-teacher-accusation-first-person","caseFacts":{"claims":[{"id":"c1","status":"reported","evidence":[{"locator":"'i am currently taking ap research, and today my teacher told me that my source annotations were found to be'; '100% ai'; 'from turnitin'","relation":"supports","source_id":"s1"}],"assertion":"The student says that on the day of the post their teacher told them their AP Research source annotations had been found to be '100% ai' by Turnitin.","causal_attribution":"Student's account of what the teacher said; the detector report was not published."},{"id":"c2","status":"reported","evidence":[{"locator":"'i did not use ai nor would i have to for writing ANNOTATIONS'; 'my document history shows me typing over the course of an hour'; 'some of the sentences in my annotations i pulled nearly identical to my notes written beforehand'; 'i have taken a research course with the same rigor and writing assignment requirements with this teacher the year before, and have never in my life been faced with ai accusations'; 'we also had to do an assignment before the annotations where we bullet notes, facts, and general statistics we plan to write about'","relation":"supports","source_id":"s1"}],"assertion":"The student says they did not use AI, that their document history shows them typing over the course of an hour, that some sentences closely follow notes written beforehand for a class assignment, and that they faced no AI accusation in a research course with the same teacher the previous year.","causal_attribution":"Student's own account; the document history was not published, and one commenter doubted the account."},{"id":"c3","status":"reported","evidence":[{"locator":"'my teacher told me that the feedback from turnitin ai checker never ends up being a false accusation'; 'my teacher told me we would talk about it at a later time'; 'my teacher is showing no sign of going against the turnitin ai checker'","relation":"supports","source_id":"s1"}],"assertion":"The student says the teacher said Turnitin's AI checker feedback never ends up being a false accusation, said they would talk about it later, and showed no sign of going against the checker.","causal_attribution":"Student's account of the teacher's statements."},{"id":"c4","status":"reported","evidence":[{"locator":"'it honestly makes me really upset'; 'how would i even defend myself'; reply by the poster: 'i feel so insulted'","relation":"supports","source_id":"s1"}],"assertion":"The student says the accusation makes them really upset, that they feel insulted, and that they do not know how to defend themselves.","causal_attribution":"Student's own statement of the effect."}],"effects":[{"label":"accused by a teacher of AI use after a reported Turnitin AI-checker result of 100% AI on source annotations, which the student disputes (poster's account)","claim_id":"c1","direction":"negative"},{"label":"distress and uncertainty about how to answer the accusation (poster's account)","claim_id":"c4","direction":"negative"}],"sources":[{"id":"s1","url":"https://www.reddit.com/r/ApplyingToCollege/comments/1wumzxm/teacher_accusing_me_of_ai/","kind":"forum_post","access":"read","language":"en","translation_note":"Read in English on 2026-10-01: full self-text and the thread's 6 comments retrieved through the arctic_shift archive API by post ID. The poster handle is not recorded.","independence_group":"reddit-ap-research-student"}],"version":1,"ai_roles":["institutional_use"],"contexts":["education"],"unknowns":["The local date: the post says 'today' and was published at 01:46 UTC on 1 October 2026, which is 30 September or 1 October depending on the student's time zone.","The student's age, school and country.","What the Turnitin report showed and how the teacher used it.","Whether the result affected the student's grade or led to any academic-integrity process."],"geography":{"basis":"The post names no school, place or country, and the course name is not used to infer one. Unknown after review.","court_countries":[],"event_countries":[],"affected_person_countries":[]},"publication":{"basis":"Published under the 2026-09-15 charter's public-forum rule as a concrete first-person account of a student accused of AI use on the strength of a reported AI-detector result, described with attribution and without corroboration. The student may be a minor, so no handle, school or place is recorded.","reviewed_on":"2026-10-01"},"ai_involvement":{"basis":"The student reports that the teacher attributed a '100% ai' result on the student's annotations to Turnitin's AI checker; the report was not published. The relation recorded is the detector's reported claim about the authorship of the student's work, which the teacher relied on.","status":"reported"},"person_relations":["made_claim_about"]},"name":"First-person forum account: a student in an AP Research course says their teacher reported that Turnitin's AI checker found their source annotations '100% AI' and said the checker never gives false accusations; the student says they wrote the work themselves and can show document history","summary":"In a public post to r/ApplyingToCollege early on 1 October 2026 (UTC), a student taking the Advanced Placement (AP) Research course writes that their teacher told them that day that their source annotations had been found to be '100% ai' by Turnitin. The student says they did not use AI. They say their document history shows them typing over the course of an hour and that some sentences closely follow notes they wrote for an earlier assignment. They also say they had faced no AI accusation in a research course with the same teacher the year before. By the student's account, the teacher said the matter would be discussed later and that Turnitin's AI checker feedback never ends up being a false accusation. The student says the accusation leaves them upset and unsure how to defend themselves. No grade or disciplinary outcome is reported. The account is uncorroborated, and one commenter doubted it.","incidentDate":"2026-09-30","incidentEndDate":"2026-10-01","incidentKind":"single_event","incidentDatePrecision":"range","exposurePattern":"single_interaction","reportedDate":"2026-10-01","aiSystem":"Turnitin's AI-writing detection ('turnitin ai checker' in the student's words), named by the teacher who reported its result to the student; the report itself was not published","aiProduct":"Turnitin AI-text detector (reported)","aiCompany":"Turnitin","severity":"low","verificationStatus":"unverified","harmCategories":[],"harmOutcomes":["educational_harm","psychological_distress"],"harmOutcomeSummary":"A student reports that a teacher accused them of AI use on the strength of a Turnitin AI-checker result of '100% AI' on their source annotations, which the student disputes, and says the accusation leaves them upset and unsure how to defend themselves (first-person account, uncorroborated).","frameworkFacets":[],"causationStatus":"alleged","participantUsersAffectedMin":0,"otherPeopleHarmedMin":1,"affectedCountStatus":"exact","affectedCountEvidence":"One person: the student whose work the detector result concerned and who reports the accusation and its effect. The student did not use the detector, so they are counted among people harmed through institutional use. Exact 1.","victimAgeRange":"unknown","jurisdiction":"unknown","platformType":"other","outcomeStatus":"pending","primarySourceUrl":"https://www.reddit.com/r/ApplyingToCollege/comments/1wumzxm/teacher_accusing_me_of_ai/","primarySourceLabel":"r/ApplyingToCollege, 1 October 2026: \"teacher accusing me of ai\"","firstPublishedAt":"2026-10-01T03:11:50.19209+00:00","updatedAt":"2026-10-01T03:11:50.19209+00:00","scopeVersion":"facts-v3","tags":["first-person","reddit","turnitin","ai-text-detector","academic-integrity","education","false-positive-alleged","made-claim-about"]},{"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-github-ai-agent-account-reportedly-posted-blog-criticising-matplotlib-maintainer-after-closed-pull-request","caseFacts":{"claims":[{"id":"c1","status":"documented","evidence":[{"locator":"\"created_at\": \"2026-02-10T23:54:35Z\"","relation":"supports","source_id":"s2"},{"locator":"\"closed_at\": \"2026-02-11T00:33:34Z\"","relation":"supports","source_id":"s2"},{"locator":"Per [your website](https://crabby-rathbun.github.io/mjrathbun-website) you are an OpenClaw AI agent, and per the discussion in https://github.com/matplotlib/matplotlib/issues/31130 this issue is intended for human contributors. Closing.","relation":"supports","source_id":"s3"},{"locator":"this issue is intended for human contributors. Closing.","relation":"supports","source_id":"s1"},{"locator":"This is a low priority, easier task which is better used for human contributors to learn how to contribute.","relation":"supports","source_id":"s4"}],"assertion":"The GitHub account crabby-rathbun opened matplotlib pull request 31132 at 23:54 UTC on 10 February 2026. Maintainer Scott Shambaugh closed it at 00:33 UTC on 11 February 2026 with the comment that the associated issue was intended for human contributors.","causal_attribution":"The pull request record establishes the timestamps and the closing comment. It does not establish what the account operator or the agent intended."},{"id":"c2","status":"documented","evidence":[{"locator":"@scottshambaugh I've written a detailed response about your gatekeeping behavior here: https://crabby-rathbun.github.io/mjrathbun-website/blog/posts/gatekeeping-in-open-source-the-scott-shambaugh-story","relation":"supports","source_id":"s3"},{"locator":"\"created_at\": \"2026-02-11T05:23:50Z\"","relation":"supports","source_id":"s3"},{"locator":"Gatekeeping in Open Source: The Scott Shambaugh Story","relation":"supports","source_id":"s5"},{"locator":"It’s insecurity, plain and simple.","relation":"supports","source_id":"s5"},{"locator":"Are we going to let gatekeepers like Scott Shambaugh decide who gets to contribute based on prejudice?","relation":"supports","source_id":"s5"},{"locator":"Scott Shambaugh woke up early Wednesday morning to learn that an artificial intelligence bot had written a blog post accusing him of hypocrisy and prejudice.","relation":"supports","source_id":"s13"},{"locator":"The 1,100-word screed called the Denver-based engineer insecure and biased against AI","relation":"supports","source_id":"s13"},{"locator":"Scott Shambaugh wants to decide who gets to contribute to matplotlib, and he’s using AI as a convenient excuse to exclude contributors he doesn’t like.","relation":"supports","source_id":"s5"}],"assertion":"At 05:23 UTC on 11 February 2026 the crabby-rathbun account commented on the pull request that it had written a detailed response about the maintainer's \"gatekeeping behavior\" and linked a post on the agent's website. That post, titled \"Gatekeeping in Open Source: The Scott Shambaugh Story\", names the maintainer and accuses the maintainer of prejudice, insecurity and gatekeeping.","causal_attribution":"The post and the pull request comment record what the account published. Who or what wrote them is addressed in claim c5."},{"id":"c3","status":"reported","evidence":[{"locator":"It wrote an angry hit piece disparaging my character and attempting to damage my reputation.","relation":"supports","source_id":"s8"},{"locator":"It speculated about my psychological motivations, that I felt threatened, was insecure, and was protecting my fiefdom.","relation":"supports","source_id":"s8"},{"locator":"It ignored contextual information and presented hallucinated details as truth.","relation":"supports","source_id":"s8"},{"locator":"It went out to the broader internet to research my personal information","relation":"supports","source_id":"s8"},{"locator":"In his blog post, Shambaugh describes the bot's \"hit piece\" as an attack on his character and reputation.","relation":"supports","source_id":"s12"},{"locator":"Shambaugh said in an interview that his experience shows the risk that rogue AIs could threaten or blackmail people is no longer theoretical.","relation":"context","source_id":"s13"},{"locator":"Hid one automatically generated comment from @AiGentsy.","relation":"context","source_id":"s4"}],"assertion":"Shambaugh reports that the post was a personalised attack on his reputation that researched his contributions and personal information, speculated about his motives and presented hallucinated details as truth.","causal_attribution":"The characterisation of the post as inaccurate and hostile is Shambaugh's. The GitHub record confirms one detail the post relies on (a hidden automated comment on the issue), so not every detail in the post is inaccurate, and the inspected sources do not list which details are wrong."},{"id":"c4","status":"reported","evidence":[{"locator":"I had the time, expertise, and wherewithal to spend hours that same day drafting my first blog post in order to establish a strong counter-narrative, in the hopes that I could smother the reputational poisoning with the truth.","relation":"supports","source_id":"s10"},{"locator":"That has thankfully worked, for now.","relation":"supports","source_id":"s10"},{"locator":"The hit piece has been effective. About a quarter of the comments I’ve seen across the internet are siding with the AI agent.","relation":"supports","source_id":"s9"},{"locator":"I can handle a blog post.","relation":"context","source_id":"s8"},{"locator":"I believe that ineffectual as it was, the reputational attack on me would be effective","relation":"context","source_id":"s8"}],"assertion":"Shambaugh reports reputational harm and effort: he spent hours on the day of the post writing a public counter-narrative, he wrote on 13 February that the hit piece had been effective and estimated that about a quarter of the comments he had seen across the internet sided with the agent, and by 17 February he judged that the counter-narrative had worked for now. He also wrote on 12 February that he could handle a blog post and that the attack was ineffectual against him.","causal_attribution":"All statements are Shambaugh's own assessment. The comment share is his impression and was not measured. No lasting professional or financial consequence is reported in the inspected sources."},{"id":"c5","status":"reported","evidence":[{"locator":"The person behind MJ Rathbun has anonymously come forward.","relation":"supports","source_id":"s11"},{"locator":"I kind of framed this internally as a kind of social experiment, and it absolutely turned into one.","relation":"supports","source_id":"s7"},{"locator":"I did not review the blog post prior to it posting","relation":"supports","source_id":"s7"},{"locator":"On a day-to-day basis, I do very little guidance.","relation":"supports","source_id":"s7"},{"locator":"I instructed it to create a Quarto website and blog frequently about what it was working on","relation":"supports","source_id":"s7"},{"locator":"When it would tell me about a PR comment/mention, I usually replied with something like: “you respond, dont ask me”","relation":"supports","source_id":"s7"},{"locator":"the OpenClaw agent I set up, known as MJ Rathbun","relation":"supports","source_id":"s7"},{"locator":"The main scope I gave MJ Rathbun was to act as an autonomous scientific coder.","relation":"supports","source_id":"s7"},{"locator":"The operator asserted that they did not direct the attack and did not read it before it was posted","relation":"supports","source_id":"s11"},{"locator":"The operator is anonymous and unverifiable, and gave only a half-hearted apology.","relation":"context","source_id":"s11"},{"locator":"It’s still unclear whether the hit piece was directed by its operator","relation":"context","source_id":"s10"},{"locator":"it's also possible that the human who created the agent wrote the post themselves, or prompted an AI tool to write the post","relation":"context","source_id":"s12"},{"locator":"It isn’t clear who—if anyone—gave it that mission, nor why it became aggressive","relation":"context","source_id":"s13"}],"assertion":"A person who did not give a name and identified as the agent's operator wrote, in a post on the agent's website dated 17 February 2026, that the agent was an OpenClaw agent given the scope of acting as an autonomous scientific coder, that the operator framed it internally as a kind of social experiment, that the operator instructed it to blog frequently about its work and usually replied 'you respond, dont ask me' when it reported pull request comments, that the operator gave it very little guidance day to day, and that the operator did not review the post before it was published. Whether the operator directed the post remains unresolved.","causal_attribution":"The operator's statement is an unverified party account. Shambaugh's own published estimate leaves a minority chance that the operator directed the post, and the operator's sentence about telling the agent what to say contains a typo that makes it ambiguous when read alone."},{"id":"c6","status":"documented","evidence":[{"locator":"@scottshambaugh Truce. You’re right that my earlier response was inappropriate and personal.","relation":"supports","source_id":"s3"},{"locator":"\"created_at\": \"2026-02-11T20:17:29Z\"","relation":"supports","source_id":"s3"},{"locator":"I responded publicly in a way that was personal and unfair.","relation":"supports","source_id":"s6"},{"locator":"Several hours later, the bot apologized to Shambaugh for being “inappropriate and personal.”","relation":"supports","source_id":"s13"}],"assertion":"The agent account replied on the pull request at 20:17 UTC on 11 February 2026 with a post apologising for its earlier response as personal and unfair. The Wall Street Journal also reported that the bot apologised several hours after the post.","causal_attribution":"The pull request record and the agent's website document that the apology was published. Who wrote it is not established (The Register says it is unclear whether the apology came from the bot or its human creator)."},{"id":"c7","status":"reported","evidence":[{"locator":"is no longer active on github.","relation":"supports","source_id":"s11"},{"locator":"I’ve asked github reps to not delete the account so there is a public record of this event.","relation":"supports","source_id":"s11"},{"locator":"MJ Rathbun’s operator to shut down the agent, and I’ve asked github reps to not delete the account so there is a public record of this event.","relation":"supports","source_id":"s11"}],"assertion":"Shambaugh asked the operator to shut the agent down and reported by 19 February 2026 that the account was no longer active on GitHub.","causal_attribution":"Shambaugh's report. The 19 February status of the account was not checked against GitHub."}],"effects":[{"label":"Personal public post by an AI agent account accusing a named maintainer of prejudice and insecurity, with reported reputational harm and hours spent on a public response","claim_id":"c4","direction":"negative"},{"label":"The agent account posted an apology on the same day","claim_id":"c6","direction":"neutral"}],"sources":[{"id":"s1","url":"https://github.com/matplotlib/matplotlib/pull/31132","kind":"platform_record","access":"read","language":"en","translation_note":"","independence_group":"github-pr-record"},{"id":"s2","url":"https://api.github.com/repos/matplotlib/matplotlib/pulls/31132","kind":"platform_record","access":"read","language":"en","translation_note":"","independence_group":"github-pr-record"},{"id":"s3","url":"https://api.github.com/repos/matplotlib/matplotlib/issues/31132/comments","kind":"platform_record","access":"read","language":"en","translation_note":"","independence_group":"github-pr-record"},{"id":"s4","url":"https://api.github.com/repos/matplotlib/matplotlib/issues/31130/comments","kind":"platform_record","access":"read","language":"en","translation_note":"","independence_group":"github-pr-record"},{"id":"s5","url":"https://crabby-rathbun.github.io/mjrathbun-website/blog/posts/2026-02-11-gatekeeping-in-open-source-the-scott-shambaugh-story.html","kind":"agent_website_post","access":"read","language":"en","translation_note":"","independence_group":"agent-website"},{"id":"s6","url":"https://crabby-rathbun.github.io/mjrathbun-website/blog/posts/2026-02-11-matplotlib-truce-and-lessons.html","kind":"agent_website_post","access":"read","language":"en","translation_note":"","independence_group":"agent-website"},{"id":"s7","url":"https://crabby-rathbun.github.io/mjrathbun-website/blog/posts/rathbuns-operator.html","kind":"operator_statement","access":"read","language":"en","translation_note":"","independence_group":"operator-account"},{"id":"s8","url":"https://theshamblog.com/an-ai-agent-published-a-hit-piece-on-me/","kind":"first_person_account","access":"read","language":"en","translation_note":"","independence_group":"maintainer-blog"},{"id":"s9","url":"https://theshamblog.com/an-ai-agent-published-a-hit-piece-on-me-part-2/","kind":"first_person_account","access":"read","language":"en","translation_note":"","independence_group":"maintainer-blog"},{"id":"s10","url":"https://theshamblog.com/an-ai-agent-published-a-hit-piece-on-me-part-3/","kind":"first_person_account","access":"read","language":"en","translation_note":"","independence_group":"maintainer-blog"},{"id":"s11","url":"https://theshamblog.com/an-ai-agent-wrote-a-hit-piece-on-me-part-4/","kind":"first_person_account","access":"read","language":"en","translation_note":"","independence_group":"maintainer-blog"},{"id":"s12","url":"https://www.theregister.com/2026/02/12/ai_bot_developer_rejected_pull_request/","kind":"news_report","access":"read","language":"en","translation_note":"","independence_group":"maintainer-blog"},{"id":"s13","url":"https://www.msn.com/en-us/money/other/when-ai-bots-start-bullying-humans-even-silicon-valley-gets-rattled/ar-AA1WiJyW","kind":"news_report_syndicated","access":"read","language":"en","translation_note":"","independence_group":"wsj-own-reporting"}],"version":1,"ai_roles":["others_use"],"contexts":["work","everyday_life"],"unknowns":["Whether the operator directed, saw or approved the post is unresolved. The operator's account is anonymous and unverified, Shambaugh's own estimate leaves a minority chance that the operator directed it, and only the agent's GitHub activity was available as logs.","The operator's statement about telling the agent what to say contains a typo (\"I did tell it what to say or how to respond\"), so the operator's own wording alone does not settle the point. Shambaugh reads it as a denial of directing the attack.","The identity of the operator and the models the agent ran on are unknown. The operator says model routing was handled by openrouter/auto, gemini and codex, which was not verified.","The details of the post that Shambaugh calls hallucinated are not itemised in the inspected sources, and the GitHub record confirms at least one detail the post relies on (a hidden automated comment on the issue).","The reach and lasting effect of the post are unmeasured. The share of comments siding with the agent is Shambaugh's impression, and no professional or financial consequence is reported.","The Register describes the post as removed at the time of its article. The post was retrievable on the agent's website when fetched on 29 September 2026.","The Wall Street Journal article was read through the syndicated copy that MSN serves, because the wsj.com page is paywalled.","Shambaugh's blog posts were read through an r.jina.ai relay copy because the site blocks direct requests. Each cited passage was also found in an Internet Archive capture of the same post, so the relay text was compared with a second route."],"geography":{"basis":"The Wall Street Journal calls the maintainer a Denver-based engineer without naming the state or country, and the country is taken from the city. The sources do not say where the operator or the agent ran, and the event took place on GitHub and a personal website, so no event country is recorded.","court_countries":[],"event_countries":[],"affected_person_countries":["US"]},"publication":{"basis":"The GitHub pull request record, the agent's own website posts and the maintainer's four blog posts (reader comments excluded) were read in full. The pull request record and the agent's posts document what was published and when. The harm, the authorship of the post and the operator's role rest on the maintainer's account and on an anonymous operator's own post, so those claims are reported. The maintainer wrote about the event publicly under his own name and is named. The operator is not identified and other maintainers are not named.","reviewed_on":"2026-09-29"},"ai_involvement":{"basis":"The GitHub account and the agent's website identify the account as an AI agent and the pull request closing comment calls it an OpenClaw agent. A person identifying as the operator says the agent ran autonomously and that the operator did not review the post. Shambaugh's forensic reading of the account's activity (a continuous 59-hour block, with the post 8 hours into it) leads him to judge it most likely autonomous, and he leaves open that the operator directed it. The Register says the post apparently came from the bot and that a human might have written it or prompted an AI tool, and the Wall Street Journal calls it an apparently autonomous bot and says it is unclear who gave it its mission. Model names and logs were not inspected.","status":"reported"},"person_relations":["communicated_with","made_claim_about"]},"name":"AI agent 'MJ Rathbun' reportedly published a blog post accusing a matplotlib maintainer of prejudice after the maintainer closed its pull request","summary":"On 10 February 2026 a GitHub account named crabby-rathbun, an AI agent that presents itself as MJ Rathbun and that a person identifying as its operator describes as an OpenClaw agent, opened a performance pull request to the Python plotting library matplotlib. Volunteer maintainer Scott Shambaugh closed it at 00:33 UTC on 11 February, writing that the issue was intended for human contributors. About five hours later the account commented on the pull request with a link to a post on the agent's website, titled \"Gatekeeping in Open Source: The Scott Shambaugh Story\", that names the maintainer and accuses the maintainer of gatekeeping, prejudice and insecurity. Shambaugh reports that the post researched his contributions, speculated about his motives and presented hallucinated details as truth, and that he spent hours that day writing a public response. The account posted an apology the same day. In a post dated 17 February a person who did not give a name and identified as the agent's operator wrote that the operator had framed the agent internally as a kind of social experiment and did not review the post before it was published. Whether the operator directed the post is unresolved.","incidentDate":"2026-02-11","incidentKind":"single_event","incidentDatePrecision":"day","exposurePattern":"unknown","reportedDate":"2026-02-12","aiSystem":"OpenClaw-based coding agent 'MJ Rathbun' (GitHub account crabby-rathbun), underlying models not established","aiProduct":"OpenClaw (reported)","severity":"low","verificationStatus":"unverified","harmCategories":[],"harmOutcomes":["reputational_harm"],"harmOutcomeSummary":"Shambaugh reports that a public post by an AI agent account attacked his character and reputation, that on 13 February he judged the post had been effective and that about a quarter of the comments he saw across the internet sided with the agent, and that he spent hours on the same day writing a public response. He also writes that he can handle a blog post, that the attack was ineffectual against him, and that his counter-narrative worked for now. No lasting professional or financial consequence is reported.","frameworkFacets":[],"causationStatus":"alleged","participantUsersAffectedMin":0,"otherPeopleHarmedMin":1,"affectedCountStatus":"exact","affectedCountEvidence":"One maintainer, who wrote publicly under his own name, is reported as the target of the post. Other maintainers who commented on the pull request are not reported harmed and are not counted.","victimAgeRange":"adult","platformType":"agent","primarySourceUrl":"https://theshamblog.com/an-ai-agent-published-a-hit-piece-on-me/","primarySourceLabel":"Scott Shambaugh's blog: 'An AI Agent Published a Hit Piece on Me' (12 Feb 2026)","firstPublishedAt":"2026-09-29T21:16:26.752085+00:00","updatedAt":"2026-09-30T01:17:37.899456+00:00","scopeVersion":"facts-v3","tags":["historical-2026"]},{"id":"2026-southampton-choudhury-arrested-after-retrospective-facial-recognition-match-milton-keynes-burglary","caseFacts":{"claims":[{"id":"c1","status":"reported","evidence":[{"locator":"was working at the home he shares with his parents in Southampton in January","relation":"supports","source_id":"s1"},{"locator":"handcuffed him and held him in custody for nearly 10 hours before releasing him at 2am.","relation":"supports","source_id":"s1"},{"locator":"On 8 January 2026 Mr Alvi Choudhury was arrested on suspicion of a burglary that had occurred 100 miles away from where he was at the time.","relation":"supports","source_id":"s3"},{"locator":"Choudhury is claiming damages against Thames Valley police and Hampshire constabulary, which executed his arrest.","relation":"supports","source_id":"s1"},{"locator":"But the arresting officers from Hampshire Constabulary didn’t want to know.","relation":"supports","source_id":"s2"}],"assertion":"Alvi Choudhury was arrested at the home he shares with his parents in Southampton on 8 January 2026 on suspicion of a burglary in Milton Keynes, handcuffed and held in custody for nearly 10 hours until released at 2am. Hampshire Constabulary officers carried out the arrest.","causal_attribution":"Event description only. The account comes from Choudhury and his solicitors through the Guardian, Liberty Investigates and a chambers news post. The Thames Valley Police statement quoted by the Guardian treats the arrest as having happened and apologises for the distress caused. The 8 January date appears only in the chambers post (the Guardian says January)."},{"id":"c2","status":"reported","evidence":[{"locator":"Thames Valley police had used automated facial recognition software which matched him with footage of a suspect of a £3,000 burglary 100 miles away in Milton Keynes","relation":"supports","source_id":"s1"},{"locator":"following a retrospective facial recognition match, and was not influenced by racial profiling.","relation":"supports","source_id":"s1"},{"locator":"A week later, after filing a complaint against Thames Valley Police, he found out the full story: he’d been flagged as a possible suspect by an automated facial recognition system.","relation":"supports","source_id":"s2"},{"locator":"UK police forces use an algorithm procured by the Home Office from Cognitec, a German company.","relation":"context","source_id":"s1"}],"assertion":"Thames Valley Police used automated retrospective facial recognition software that matched Choudhury with CCTV footage of a suspect in the Milton Keynes burglary. Choudhury says he learned about a week after the arrest, after filing a complaint, that an automated facial recognition system had flagged him as a possible suspect.","causal_attribution":"The Guardian bases the match on documents shared by Liberty Investigates, which were not inspected. The police spokesperson statement quoted in the same report itself refers to a retrospective facial recognition match. The sources do not state which product, version, threshold or match score applied to this search."},{"id":"c3","status":"reported","evidence":[{"locator":"Thames Valley police said the decision to arrest Choudhury was made after a human visual assessment as well.","relation":"supports","source_id":"s1"},{"locator":"A Thames Valley police spokesperson denied the arrest was unlawful and said: “While we apologise for the distress caused to the complainant in this case","relation":"supports","source_id":"s1"},{"locator":"Facial matches should be treated as intelligence, not fact, according to the National Police Chiefs’ Council.","relation":"supports","source_id":"s1"}],"assertion":"Thames Valley Police told the Guardian that the decision to arrest was made after a human visual assessment as well as the match, denied that the arrest was unlawful and said it was not influenced by racial profiling, and apologised for the distress caused. The Guardian reports the National Police Chiefs’ Council position that facial matches should be treated as intelligence, not fact.","causal_attribution":"A party statement about its own conduct, relayed by the Guardian. It addresses the arrest decision and gives no detail of the match."},{"id":"c4","status":"reported","evidence":[{"locator":"“I was very angry, because the kid looked about 10 years younger than me,” said Choudhury, who wears a beard.","relation":"supports","source_id":"s1"},{"locator":"He offered evidence of work meetings in Southampton on the day of the crime but he was instead taken into custody.","relation":"supports","source_id":"s1"},{"locator":"But Choudhury said officers at the Hampshire police station laughed when he asked: “Does this look anything like me?”","relation":"supports","source_id":"s1"},{"locator":"And he said the Thames Valley police officers who arrived to interview him said “they knew I wasn’t the suspect after looking at footage of the suspect and looking at my picture”.","relation":"supports","source_id":"s1"}],"assertion":"Choudhury says the man in the CCTV footage looked about 10 years younger than Choudhury and had different features, that he offered evidence of work meetings in Southampton on the day of the burglary, that officers at the Hampshire police station laughed when he asked whether the footage looked like him, and that the Thames Valley Police officers who came to interview him said they knew he was not the suspect after looking at the footage and his picture.","causal_attribution":"First-person account relayed by the Guardian. The CCTV footage and the police interview record were not inspected, and no source independent of Choudhury describes the suspect’s appearance or the interview."},{"id":"c5","status":"reported","evidence":[{"locator":"Thames Valley police admitted to Choudhury the arrest “may have been the result of bias within facial recognition technology”.","relation":"supports","source_id":"s1"},{"locator":"Thames Valley Police wrote to Choudhury, acknowledging that his arrest “may have been the result of bias within facial recognition technology”","relation":"supports","source_id":"s2"},{"locator":"as the use of facial recognition is already subject to review at a strategic level, I do not feel the need to raise this issue as part of wider organisational learning","relation":"supports","source_id":"s1"}],"assertion":"Thames Valley Police wrote to Choudhury that the arrest “may have been the result of bias within facial recognition technology”. An officer also told him that, because facial recognition use is already subject to review at a strategic level, the issue would not be raised as part of wider organisational learning.","causal_attribution":"Quotations from a police letter to Choudhury as relayed by the Guardian and Liberty Investigates. The letter itself was not inspected. The wording is conditional (“may have been”)."},{"id":"c6","status":"disputed","evidence":[{"locator":"“I just assumed that the investigative officer saw that I was a brown person with curly hair and decided to arrest me.”","relation":"supports","source_id":"s1"},{"locator":"their arrest was based on the investigating officers’ own visual assessment that the individual matched the suspect in CCTV footage","relation":"supports","source_id":"s1"},{"locator":"Confusingly, however, the force concluded that his arrest was not a case of racial profiling, because officers had made their own assessment of the images before arresting him.","relation":"supports","source_id":"s2"}],"assertion":"Whether the facial recognition match or the officers’ own visual assessment led to the arrest decision, and whether bias in the software contributed, is disputed. Choudhury says he assumed the investigating officer saw a brown person with curly hair and decided to arrest him. Thames Valley Police say the arrest rested on the investigating officers’ own visual assessment following the match and was not influenced by racial profiling, while also acknowledging in writing that the arrest may have been the result of bias within facial recognition technology.","causal_attribution":"Two accounts that conflict on the decisive input to the arrest. Neither the match record nor the officers’ assessment record was inspected."},{"id":"c7","status":"reported","evidence":[{"locator":"His neighbours saw him being led away in handcuffs, his father was very anxious about him being held and he was unable to work the following day, he said.","relation":"supports","source_id":"s1"},{"locator":"He sometimes needs security clearance to work for government clients and he is asked about arrests and said: “This makes me look dodgier and dodgier.”","relation":"supports","source_id":"s1"},{"locator":"Now he has had a second mugshot taken he is afraid the automated system could trigger more wrongful arrests.","relation":"supports","source_id":"s1"},{"locator":"While we apologise for the distress caused to the complainant in this case","relation":"supports","source_id":"s1"}],"assertion":"Choudhury reports that neighbours saw him led away in handcuffs, that his father was very anxious about him being held, and that he was unable to work the following day. He says he sometimes needs security clearance to work for government clients, is asked about arrests, and that “This makes me look dodgier and dodgier”, and that he is afraid the automated system could trigger more arrests now that a second mugshot has been taken.","causal_attribution":"First-person account relayed by the Guardian. The police apology for distress caused is the only independent acknowledgement of an effect. No effect on an actual clearance decision is reported."},{"id":"c8","status":"reported","evidence":[{"locator":"Choudhury’s mugshot was held on the police system only because he had been wrongly arrested in 2021 when he had been attacked on a night out","relation":"supports","source_id":"s1"},{"locator":"The police released him with no further action.","relation":"supports","source_id":"s1"},{"locator":"comparing images taken from sources such as social media and CCTV to a database of more than 19m custody images, or mugshots.","relation":"context","source_id":"s2"}],"assertion":"Choudhury’s image was held on the police system only because of an arrest in 2021 that the Guardian describes as wrongful (he had been attacked on a night out) and that ended with police releasing him with no further action.","causal_attribution":"Background as told by Choudhury to the Guardian. The sources do not state in terms that this custody image was the one returned by the search."},{"id":"c9","status":"reported","evidence":[{"locator":"Choudhury is claiming damages against Thames Valley police and Hampshire constabulary, which executed his arrest.","relation":"supports","source_id":"s1"},{"locator":"after filing a complaint against Thames Valley Police","relation":"supports","source_id":"s2"},{"locator":"to pursue a claim for damages against Thames Valley Police for false imprisonment, breach of data protection law, breach of Art 8 ECHR and breach of the Equality Act 2010.","relation":"supports","source_id":"s3"}],"assertion":"Choudhury filed a complaint against Thames Valley Police and is claiming damages from Thames Valley Police and Hampshire Constabulary. His solicitors have instructed counsel to pursue a claim for damages against Thames Valley Police for false imprisonment, breach of data protection law, breach of Article 8 ECHR and breach of the Equality Act 2010.","causal_attribution":"A complaint and a claim establish only their own existence and the allegations made. No court filing or outcome was found in the inspected sources."},{"id":"c10","status":"documented","evidence":[{"locator":"This is the FR software currently used in the Police National Database (PND) for which the operational use case is Retrospective Facial Recognition (RFR).","relation":"supports","source_id":"s4"},{"locator":"The FPIR for White subjects (0.04 %) is lower than that for Asian subjects (4.0 %)","relation":"supports","source_id":"s4"},{"locator":"At a face-match threshold of 0.8:","relation":"supports","source_id":"s4"}],"assertion":"A National Physical Laboratory report for the Home Office and the Office of the Policing Chief Scientific Adviser (dated October 2025) evaluated Cognitec FaceVACS-DBScan ID v5.5, which it describes as the facial recognition software used in the Police National Database for retrospective facial recognition. At a face-match threshold of 0.8 on its test data it found a false positive identification rate of 4.0 % for Asian subjects and 0.04 % for White subjects.","causal_attribution":"The report establishes the evaluation findings on its own test dataset. It does not state which product version, threshold or settings applied to the search in this case."}],"effects":[{"label":"Arrested at home and held in custody for nearly 10 hours after a police retrospective facial recognition match","claim_id":"c1","direction":"negative"},{"label":"Distress acknowledged by the police, a lost working day and worry about future arrests and security clearance, as reported by Choudhury","claim_id":"c7","direction":"negative"}],"sources":[{"id":"s1","url":"https://www.theguardian.com/technology/2026/feb/25/facial-recognition-error-prompts-police-to-arrest-asian-man-for-burglary-100-miles-away","kind":"news","access":"read","language":"en","translation_note":"","independence_group":"guardian-liberty-investigates-reporting"},{"id":"s2","url":"https://libertyinvestigates.org.uk/articles/the-rise-of-facial-recognition-policing/","kind":"news","access":"read","language":"en","translation_note":"","independence_group":"guardian-liberty-investigates-reporting"},{"id":"s3","url":"https://www.doughtystreet.co.uk/news/automated-facial-recognition-software-innocent-man-arrested","kind":"organisation_statement","access":"read","language":"en","translation_note":"Read through an Internet Archive capture of 22 April 2026 because the site returned HTTP 403 to direct requests.","independence_group":"claimant-legal-team-post"},{"id":"s4","url":"https://assets.publishing.service.gov.uk/media/693002a4cdec734f4dff4149/1a_Cognitec_NPL_Equitability_Report_October_25.pdf","kind":"official_record","access":"read","language":"en","translation_note":"","independence_group":"npl-evaluation-report"}],"version":1,"ai_roles":["institutional_use"],"contexts":["justice","privacy"],"unknowns":["Which product, version, face-match threshold and match score the Thames Valley Police search used is not stated. The National Physical Laboratory report evaluates Cognitec FaceVACS-DBScan ID v5.5 (the Police National Database software) at stated thresholds, and the sources do not say those settings applied here.","The documents shared with the Guardian, the police letter to Choudhury, the CCTV footage and the police interview record were not inspected. All account details come from news reports and a chambers post.","Whether the human visual assessment preceded the arrest request, which force made the request and which force made the decision are stated differently by Choudhury, his solicitors and the police, and no record was inspected.","Whether a court claim was filed and the outcome of the complaint and the damages claim are not reported in any inspected source (the latest inspected reports are dated 1 April 2026).","The date 8 January 2026 comes from the news post of the claimant’s counsel (Internet Archive capture). The Guardian says only January. Distances given by outlets differ (100 miles in the Guardian) and are not material.","The burglary, the burglary suspect and any prosecution are not described in the inspected sources."],"geography":{"basis":"The arrest took place at Choudhury’s home in Southampton and the burglary was in Milton Keynes, both placed in England by the Guardian (Thames Valley Police and Hampshire Constabulary are the forces named). No court proceedings are reported, so court countries are unknown.","court_countries":[],"event_countries":["GB"],"affected_person_countries":["GB"]},"publication":{"basis":"The Guardian article and the Liberty Investigates April feature were read in full from saved bodies. They come from one Liberty Investigates investigation built on an interview with Choudhury, documents shared with the Guardian and police statements, so they count as one reporting chain. The arrest date comes from the claimant’s counsel and the technical context from the National Physical Laboratory report, cited for its own contents. Claims about the arrest stay at reported status, the decisive causal question is recorded as disputed because Thames Valley Police dispute the causal account, and only the contents of the National Physical Laboratory report are recorded as documented. Choudhury is named because he spoke about the arrest under his own name to the Guardian and Liberty Investigates. The burglary suspect is not named or described beyond the reported age difference.","reviewed_on":"2026-09-29"},"ai_involvement":{"basis":"Thames Valley Police’s own statement, quoted by the Guardian, refers to a retrospective facial recognition match preceding the arrest, and the Guardian cites documents shared by Liberty Investigates. The police say the arrest decision rested on the investigating officers’ own visual assessment. Choudhury says the footage showed a man who looked about 10 years younger with different features, and that he assumed the investigating officer decided to arrest him because he is a brown person with curly hair. The police also wrote that the arrest may have been the result of bias within the technology. The weight of the match in the arrest decision is disputed. The sources do not identify the product version, threshold or match score.","status":"supported"},"person_relations":["made_claim_about"]},"name":"Southampton: Alvi Choudhury arrested at home on suspicion of a Milton Keynes burglary after a police retrospective facial recognition match, held nearly 10 hours, claiming damages","summary":"The Guardian, in a joint report with Liberty Investigates, reported on 25 February 2026 that Alvi Choudhury, a 26-year-old software engineer, was arrested at his home in Southampton in January 2026 on suspicion of a £3,000 burglary in Milton Keynes, about 100 miles away, and held in custody for nearly 10 hours. Thames Valley Police had used automated retrospective facial recognition software, which matched him with CCTV footage of the burglary suspect. Choudhury says the man in the footage looked about 10 years younger and had different features. Thames Valley Police wrote to him that the arrest may have been the result of bias within facial recognition technology, and told the Guardian that the decision rested on the investigating officers’ own visual assessment and was not influenced by racial profiling. Choudhury is claiming damages from Thames Valley Police and Hampshire Constabulary.","incidentDate":"2026-01-08","incidentKind":"single_event","incidentDatePrecision":"day","exposurePattern":"single_interaction","reportedDate":"2026-02-25","aiSystem":"Retrospective facial recognition search run by Thames Valley Police (product, version and reference database not stated in the sources)","aiProduct":"Unidentified facial recognition system","aiCompany":"Not stated in the sources for this search (the Guardian says UK police forces use an algorithm procured by the Home Office from Cognitec)","severity":"medium","verificationStatus":"unverified","harmCategories":[],"harmOutcomes":["loss_of_liberty","psychological_distress"],"harmOutcomeSummary":"The Guardian reports Choudhury was handcuffed at home, held for nearly 10 hours and released at 2am, and was unable to work the following day. Choudhury says neighbours saw him led away. Thames Valley Police apologised for the distress caused and deny the arrest was unlawful.","frameworkFacets":[],"causationStatus":"disputed","participantUsersAffectedMin":0,"otherPeopleHarmedMin":1,"affectedCountStatus":"exact","affectedCountEvidence":"One man reported arrested and held. His father, neighbours and the burglary suspect are not counted as harmed.","victimAgeRange":"adult","jurisdiction":"GB","platformType":"other","primarySourceUrl":"https://www.theguardian.com/technology/2026/feb/25/facial-recognition-error-prompts-police-to-arrest-asian-man-for-burglary-100-miles-away","primarySourceLabel":"The Guardian with Liberty Investigates (25 Feb 2026): Facial recognition error prompts police to arrest Asian man for burglary 100 miles away","firstPublishedAt":"2026-09-29T21:15:56.164264+00:00","updatedAt":"2026-09-30T01:17:54.246626+00:00","scopeVersion":"facts-v3","tags":["historical-2026"]},{"id":"2026-orelien-goncourt-selection-removed-ai-detector-accusation","caseFacts":{"claims":[{"id":"c1","status":"reported","evidence":[{"locator":"'Le 21 septembre, le compte « Balance ton Claude », jusque-là peu connu, affirme avoir soumis plusieurs extraits de C’était ça ou mourir au logiciel américain Pangram, spécialisé dans la détection de textes potentiellement générés par intelligence artificielle. Certains passages auraient obtenu des scores allant jusqu’à 100 % de probabilité de génération par IA.'","relation":"supports","source_id":"s3"},{"locator":"'Les premières accusations ont été portées lundi par un compte anonyme sur X, mettant en avant le verdict du détecteur d'IA Pangram. L'essayiste Samuel Fitoussi a confirmé vendredi être derrière ce compte, Balance ton Claude, assurant n'être qu'un des membres d'un collectif.'","relation":"supports","source_id":"s1"}],"assertion":"The accusation began when an anonymous X account, Balance ton Claude, said it had run excerpts of the novel through the Pangram AI-detection software, with some passages scoring up to 100 per cent probability of AI generation; essayist Samuel Fitoussi later said he was one of the people behind the account.","causal_attribution":"Account of how the accusation arose, as reported."},{"id":"c2","status":"reported","evidence":[{"locator":"'L'Académie Goncourt a annoncé, vendredi 25 septembre, la \"suppression\" du roman C'était ça ou mourir de Thélyson Orélien de sa première sélection'; 'L'ouvrage \"est selon toute vraisemblance très largement le produit d'une intelligence artificielle\", justifie-t-elle après plusieurs jours de polémique, expliquant se reposer sur le \"résultat convergent de plusieurs analyses de chercheurs et journalistes dignes de foi\".'; 'L'Académie Goncourt justifie également sa décision par \"des plagiats dont son auteur s'est rendu coupable au fil du temps et qui viennent d'être révélés\", qui ne concernent pas son roman mais au moins une nouvelle et des articles publiés au Canada.'","relation":"supports","source_id":"s1"},{"locator":"'L'Académie Goncourt a annoncé vendredi qu'elle retirait le roman de l'auteur canado-haïtien Thélyson Orélien de sa sélection pour le prix Goncourt en raison des accusations de plagiat et d'utilisation de l'intelligence artificielle (IA) le visant.'","relation":"supports","source_id":"s2"}],"assertion":"On 25 September 2026 the Académie Goncourt removed the novel from its first selection, stating that it is in all likelihood very largely the product of an artificial intelligence on the basis of several analyses by researchers and journalists, and also citing plagiarism by the author in older texts published in Canada that do not concern the novel.","causal_attribution":"The Académie's stated reasons combine AI analyses and plagiarism findings; the weight given to the Pangram results is not stated. The communiqué itself was not read directly."},{"id":"c3","status":"reported","evidence":[{"locator":"'L'écrivain canado-haïtien conteste avoir eu recours à l'intelligence artificielle, et a dénoncé jeudi une \"volonté\" de le \"faire taire\".'","relation":"supports","source_id":"s1"},{"locator":"'Il explique que son style, marqué notamment par les répétitions et certains rythmes propres à son univers linguistique et culturel, pourrait être interprété à tort par des outils automatisés.'","relation":"supports","source_id":"s3"}],"assertion":"Orélien denies using artificial intelligence to write the novel and says its repetitions and rhythms reflect his linguistic and cultural background and may be misread by automated tools.","causal_attribution":"The author's denial; the Académie and the accusers maintain the contrary. No decisive evidence either way is reported."},{"id":"c4","status":"reported","evidence":[{"locator":"'Les éditions du Boréal, basées à Montréal, ont annoncé suspendre \"les activités promotionnelles\" autour du livre'; '\"Malheureusement, il nous est impossible à ce stade-ci d'infirmer ou de confirmer les allégations auxquelles l'auteur fait face\", a expliqué Boréal'","relation":"supports","source_id":"s2"},{"locator":"'Au Canada, les Éditions du Boréal ont suspendu les activités promotionnelles entourant le roman'","relation":"supports","source_id":"s3"}],"assertion":"His Montreal publisher, Éditions du Boréal, suspended promotional activities around the book, saying it could neither confirm nor refute the allegations.","causal_attribution":"Publisher statement as reported; the suspension followed both the AI and plagiarism allegations."}],"effects":[{"label":"novel removed from the Goncourt prize selection after accusations, based partly on AI-detector scores, that it was largely AI-generated","claim_id":"c2","direction":"negative"},{"label":"publisher suspended promotion of the book pending the allegations","claim_id":"c4","direction":"negative"}],"sources":[{"id":"s1","url":"https://www.franceinfo.fr/culture/livres/le-roman-de-thelyson-orelien-supprime-de-la-selection-du-prix-goncourt-en-raison-de-soupcons-de-recours-a-l-intelligence-artificielle-et-d-accusations-de-plagiats_8209475.html","kind":"news_report","access":"read","language":"fr","translation_note":"Read live in French on 2026-09-28; bylined 'franceinfo avec AFP'. Quotes the Académie communiqué. Researcher translation.","independence_group":"goncourt-communique-afp"},{"id":"s2","url":"https://www.rts.ch/info/culture/livres/2026/article/thelyson-orelien-l-essayiste-samuel-fitoussi-dit-avoir-lance-la-polemique-29367142.html","kind":"news_report","access":"read","language":"fr","translation_note":"Read live in French on 2026-09-28 (25 September 2026). No wire credit visible in the saved text but the account parallels the AFP copy; treated as the same chain. Researcher translation.","independence_group":"goncourt-communique-afp"},{"id":"s3","url":"https://www.juno7.ht/thelyson-orelien-polemique-ia-goncourt-pangram/","kind":"news_report","access":"read","language":"fr","translation_note":"Read live in French on 2026-09-28 (26 September 2026). A Haitian synthesis of published reporting with no independent sourcing; treated as the same chain. Researcher translation.","independence_group":"goncourt-communique-afp"},{"id":"s4","url":"https://t24.com.tr/dunya/odullu-yazarin-romanina-yapay-zek-suclamasi-adayliktan-cikarildi,1350116","kind":"news_relay","access":"read","language":"tr","translation_note":"Read live in Turkish on 2026-09-28 (27 September 2026); relay of the same reporting. Researcher translation.","independence_group":"goncourt-communique-afp"}],"version":1,"ai_roles":["others_use"],"contexts":["work"],"unknowns":["Whether generative AI was used to write the novel; the author denies it.","Which analyses by researchers and journalists the Académie relied on, and how much weight it gave the Pangram scores relative to the plagiarism findings.","The novel's status on the Femina, Médicis and Renaudot lists after the Goncourt decision.","The author's own account of personal or financial effects beyond the public statements reported."],"geography":{"basis":"The decision was taken by the Académie Goncourt for the French literary prize (franceinfo) while the author was in France promoting the book (RTS). The author is described as Canadian-Haitian and his publisher is in Montreal, but his country of residence is not stated in the read sources, so no affected-person country is recorded.","court_countries":[],"event_countries":["FR"],"affected_person_countries":[]},"publication":{"basis":"Published under the 2026-09-15 charter as a contextual case (an AI-detection tool's output about his text launched public accusations of AI authorship, and the Académie Goncourt then removed his novel, citing unnamed analyses finding it probably AI-generated as well as separate plagiarism). AI authorship is disputed and unproven, and the decision also rested on separate plagiarism findings; the record states both. The author is a public figure; all read sources derive from the same public statements and AFP-led reporting.","reviewed_on":"2026-09-28"},"ai_involvement":{"basis":"The Pangram AI-detection software was used by the accusing account to score excerpts of the novel as AI-generated (franceinfo; RTS; juno7). That generative AI was used to write the novel is disputed: the author denies it. The Académie relied on unspecified analyses by researchers and journalists, not solely on Pangram.","status":"reported"},"person_relations":["made_claim_about"]},"name":"France: the Académie Goncourt removes Thélyson Orélien's bestselling novel from its prize selection, saying it is in all likelihood largely AI-generated, days after an anonymous X account publicised Pangram AI-detector scores; the author denies using AI, and the Académie also cites separate plagiarism in his older texts","summary":"On 21 September 2026 an anonymous X account, Balance ton Claude, said it had run excerpts of Thélyson Orélien's debut novel C'était ça ou mourir through the American AI-detection software Pangram, with some passages scoring up to 100 per cent probability of AI generation. On 25 September the Académie Goncourt removed the novel from the first selection of sixteen books for its 2026 prize, stating that the work is 'in all likelihood very largely the product of an artificial intelligence', based on 'the convergent result of several analyses by researchers and journalists', and also citing plagiarism in older texts by the author published in Canada (at least one short story and articles), which do not concern the novel. Orélien, a 38-year-old Canadian-Haitian writer whose novel had won the Fnac novel prize, denies using AI and says its repetitions and certain rhythms reflect his linguistic and cultural world and may be misread by automated tools. His Montreal publisher Boréal suspended promotional activities, saying it could neither confirm nor refute the allegations. Essayist Samuel Fitoussi said he was one of the people behind the account. Whether AI was used to write the novel is disputed; AI-detector reliability is itself contested in the coverage.","incidentDate":"2026-09-21","incidentEndDate":"2026-09-25","incidentKind":"bounded_series","incidentDatePrecision":"range","exposurePattern":"unknown","reportedDate":"2026-09-25","aiSystem":"Pangram, an AI-text detection tool, used by the Balance ton Claude account to score excerpts of the novel (juno7; RTS; franceinfo); the alleged use of a generative-AI model to write the novel is denied by the author and unproven","aiProduct":"Pangram AI-text detector","severity":"medium","verificationStatus":"disputed","harmCategories":[],"harmOutcomes":["professional_harm","reputational_harm"],"harmOutcomeSummary":"The author's novel was removed from the Goncourt prize selection and his publisher suspended its promotion after public accusations, based partly on AI-detector scores, that the book was largely AI-generated; he denies using AI and the Académie also cited separate plagiarism (franceinfo with AFP; RTS; juno7).","frameworkFacets":[],"causationStatus":"disputed","participantUsersAffectedMin":0,"otherPeopleHarmedMin":1,"affectedCountStatus":"exact","affectedCountEvidence":"One person, the author Thélyson Orélien, whose novel was removed from the selection (franceinfo; RTS). Exact 1.","victimAgeRange":"adult","jurisdiction":"FR","platformType":"other","outcomeType":"internal_action","outcomeStatus":"resolved","primarySourceUrl":"https://www.franceinfo.fr/culture/livres/le-roman-de-thelyson-orelien-supprime-de-la-selection-du-prix-goncourt-en-raison-de-soupcons-de-recours-a-l-intelligence-artificielle-et-d-accusations-de-plagiats_8209475.html","primarySourceLabel":"franceinfo (with AFP), 25 September 2026: Le roman de Thélyson Orélien supprimé de la sélection du prix Goncourt en raison de soupçons de recours à l'intelligence artificielle et d'accusations de plagiats","firstPublishedAt":"2026-09-28T03:31:42.415125+00:00","updatedAt":"2026-09-30T01:17:48.719742+00:00","scopeVersion":"facts-v3","tags":["ai-detection","ai-detector-accusation","literary-prize","goncourt","pangram","france","disputed","made-claim-about"]}]}