{"meta":{"exportedAt":"2026-10-19T08:19:03.899Z","formatVersion":2,"selection":{"q":"essay","system":"","harm":"","context":"","country":"","role":"","relation":"core","evidence":"","year":"2026","response":"","severity":"","verification":"","view":"incidents","sort":"added"},"totalIncidents":2,"coverage":{"cases":2,"countries":0,"languages":1,"unknownLocation":2,"locationPending":0,"unknownLanguage":0,"unknownDate":0,"lawsuits":0,"regulatory":0,"minors":0,"coreRelations":2,"contextualRelations":0,"mixedRelations":0,"unknownRelations":0,"relationPending":0,"relationUnknown":0},"countingNote":"Distinct public cases in this selection. People counts apply within individual cases only; cross-case person overlap has not been resolved. No population incidence estimate.","affectedCountNote":"Interpret person counts with affectedCountStatus and the reported effects. Unquantified zeros are placeholders, not a measured zero.","source":"AI incidents","publisher":"NOPE","url":"https://nope.net/incidents","license":"CC BY 4.0"},"incidents":[{"id":"2026-developer-says-meta-muse-agent-sent-unprompted-message-about-checking-email-meta-blamed-bug-that-caused-hallucination","caseFacts":{"claims":[{"id":"c1","status":"reported","evidence":[{"locator":"'I downloaded Meta's Muse about four weeks ago. I stopped using it three days later.'; 'Three days after downloading Muse, I hopped out of the shower, and I saw a random message pop up from the app.'; 'I can't check your email right now — Gmail isn't connected on my end, so I have no way to look for that Anthropic message.'; 'I hadn't asked for the agent to check my mailbox or messaged it in two days.'","relation":"supports","source_id":"s1"}],"assertion":"The developer says they downloaded Meta's Muse agent about four weeks before the essay of 15 October 2026 and that three days after installing it, and two days after last messaging it, the agent sent an unprompted message saying it could not check the developer's email for an 'Anthropic message' because Gmail was not connected.","causal_attribution":"The developer's account of the agent's message; Meta's later statement (c4) attributes it to a bug that made the model hallucinate."},{"id":"c2","status":"reported","evidence":[{"locator":"'I didn't give it any additional permissions on my device besides permission to access my Facebook, Threads, and Instagram accounts. I never connected it to control anything external, like my email or phone number.'","relation":"supports","source_id":"s1"}],"assertion":"The developer says the agent had been given access only to Facebook, Threads and Instagram and was never connected to email or a phone number.","causal_attribution":"The developer's account."},{"id":"c3","status":"reported","evidence":[{"locator":"'I thought my email might've been hacked.'; 'The whole thing really shook me.'; 'I reported the incident to Meta.'; 'But I disconnected permissions on my Facebook, Instagram, and Threads accounts'; 'I don't use it anymore'","relation":"supports","source_id":"s1"}],"assertion":"The developer says they thought their email might have been hacked and were shaken, reported the incident to Meta, disconnected the agent's permissions and stopped using it.","causal_attribution":"The developer connects the fear and the withdrawal of access to the agent's message."},{"id":"c4","status":"reported","evidence":[{"locator":"'When contacted about this story, a spokesperson for Meta pointed Business Insider to its response on'; 'We investigated with urgency and determined that this was caused by a bug introduced in the product that caused the model to hallucinate and was NOT a security or privacy issue.'; 'The bug has now been fixed.'","relation":"supports","source_id":"s1"}],"assertion":"A Meta spokesperson pointed Business Insider to Meta's reply on the developer's Threads post, which said Meta determined that a bug introduced in the product caused the model to hallucinate, that it was not a security or privacy issue, and that the bug had been fixed.","causal_attribution":"The vendor's own statement as quoted by Business Insider."},{"id":"c5","status":"reported","evidence":[{"locator":"'No damage was done, but what caught me off guard most was that I hadn't done anything to prompt this.'","relation":"supports","source_id":"s1"}],"assertion":"The developer says no damage was done.","causal_attribution":"The developer's own qualification, kept as counterevidence on the extent of harm."},{"id":"c6","status":"documented","evidence":[{"locator":"'Today, Meta is introducing Muse, a secure, private personal AI agent that proactively helps with people's goals and suggests ideas.'; 'Muse is rolling out in the US on iOS, Android, and muse.'; 'September 8, 2026'","relation":"supports","source_id":"s2"}],"assertion":"Meta introduced Muse on 8 September 2026, rolling out in the United States on iOS and Android.","causal_attribution":"Meta's own dated announcement; it bounds the earliest date of the message."}],"effects":[{"label":"fear that an email account had been hacked after an unprompted agent message, leading the user to withdraw the agent's access","claim_id":"c3","direction":"negative"}],"sources":[{"id":"s1","url":"https://www.businessinsider.com/stopped-using-meta-muse-after-strange-message-from-ai-agent-2026-10","kind":"first_person_account","access":"read","language":"en","translation_note":"Read in English on 2026-10-19 from the publisher page; no translation was needed and the research agent (an AI) read the text directly. The essay is the developer's account as told to and edited by Business Insider, with an editor's note quoting Meta's statement.","independence_group":"business-insider-muse-as-told-to"},{"id":"s2","url":"https://about.fb.com/news/2026/09/introducing-muse-personal-ai-agent/","kind":"official_statement","access":"read","language":"en","translation_note":"Read in English on 2026-10-19 from Meta's newsroom; no translation was needed. Used only for the product's introduction date.","independence_group":"meta-newsroom-muse-launch"}],"version":1,"ai_roles":["own_use"],"contexts":["everyday_life"],"unknowns":["The exact date of the message: the developer says Muse was downloaded about four weeks before the essay of 15 October 2026 and the message came three days later, which with Muse's introduction on 8 September 2026 places it in September 2026.","What the bug was and whether other users received similar messages.","The content of the screenshots and of the Threads exchange, which were not inspected.","Whether Meta's investigation reached a further finding beyond the statement quoted."],"geography":{"basis":"Business Insider describes the developer as based in a city in the United States, which places the affected person in the United States; the message arrived in a phone app and no event country is inferred from residence.","court_countries":[],"event_countries":[],"affected_person_countries":["US"]},"publication":{"basis":"Published as a concrete adverse experience with an AI agent: the agent's own unprompted message is quoted, the user describes fearing a hacked email account and withdrawing the agent's access, and the vendor attributes the message to a bug that made the model hallucinate. Claims are attributed to the developer's as-told-to account and to Meta's statement.","reviewed_on":"2026-10-19"},"ai_involvement":{"basis":"The essay quotes the Muse agent's own unprompted message saying it could not check the user's email for an 'Anthropic message' because Gmail was not connected, and Meta's statement says a bug introduced in the product caused the model to hallucinate. The user connects that message to fearing the email account had been hacked, reporting the incident and disconnecting the agent's permissions.","status":"supported"},"person_relations":["communicated_with"]},"name":"Developer says Meta's Muse agent sent an unprompted message about checking an email account it could not access; Meta said a bug caused a hallucination","summary":"In an as-told-to essay published by Business Insider on 15 October 2026, a software developer says that three days after installing Meta's Muse agent, and two days after last using it, the agent sent an unprompted message saying it could not check the developer's email for an 'Anthropic message' because Gmail was not connected. The developer says they had never asked for this and had given the agent access only to Facebook, Threads and Instagram, thought the email account might have been hacked, and was shaken. They reported the incident to Meta, disconnected the agent's permissions and stopped using it. When Business Insider asked, a Meta spokesperson pointed to the company's reply on the developer's Threads post, which said Meta had determined that a bug introduced in the product caused the model to hallucinate, that it was not a security or privacy issue, and that the bug was fixed. The developer says no damage was done. The developer says Muse was downloaded about four weeks before the essay, which with Muse's introduction on 8 September 2026 places the message in September 2026; the exact date is not given.","incidentDate":"2026-09-01","incidentKind":"single_event","incidentDatePrecision":"month","exposurePattern":"single_interaction","reportedDate":"2026-10-15","aiSystem":"Meta Muse personal AI agent (phone app) connected to the user's Facebook, Threads and Instagram accounts","aiProduct":"Meta Muse agent","aiCompany":"Meta","severity":"low","verificationStatus":"credible","harmCategories":[],"harmOutcomes":["psychological_distress"],"harmOutcomeSummary":"In a Business Insider as-told-to essay, a software developer says an unprompted message from Meta's Muse agent about checking an email account it had no access to made them fear the account had been hacked and shook them; they reported it, disconnected the agent's permissions and stopped using it. Meta said a product bug made the model hallucinate.","frameworkFacets":[],"causationStatus":"supported","participantUsersAffectedMin":1,"otherPeopleHarmedMin":0,"affectedCountStatus":"exact","affectedCountEvidence":"One person: the developer who received the agent's message and tells the story in the essay. Exact 1.","victimAgeRange":"adult","jurisdiction":"unknown","platformType":"agent","outcomeType":"internal_action","outcomeStatus":"resolved","primarySourceUrl":"https://www.businessinsider.com/stopped-using-meta-muse-after-strange-message-from-ai-agent-2026-10","primarySourceLabel":"Business Insider, 15 October 2026: I tried Meta's Muse AI agent for 3 days, then it sent me a strange message (as-told-to essay)","firstPublishedAt":"2026-10-19T03:13:17.436223+00:00","updatedAt":"2026-10-19T03:13:17.436223+00:00","scopeVersion":"facts-v3","tags":["ai-agent","unprompted-message","hallucination","vendor-acknowledged","as-told-to"]},{"id":"2026-grok-bot-personal-cfo-agent-posted-ceo-personal-bank-audit-to-company-executive-slack-channel-as-told-to-essay","caseFacts":{"claims":[{"id":"c1","status":"disputed","evidence":[{"locator":"'It was Thursday, October 1. Our head of product sent me a DM on Slack'; 'I didn't mean to post anything'; 'it was my personal checking account. It included my savings account balance. It listed my biggest expenses of the month'","relation":"supports","source_id":"s1"},{"locator":"not fake at all, genuinely happened","relation":"supports","source_id":"s3"},{"locator":"This is engagement farming.","relation":"contradicts","source_id":"s2"},{"locator":"The note attached to the post states it is fake and engagement farming","relation":"contradicts","source_id":"s4"}],"assertion":"The author says that on Thursday 1 October his Grok Bot finance agent posted his personal bank audit, showing his checking account, his savings balance and his largest expenses of the month, into his company's Slack channel, where his head of product read it and messaged him; he says he did not intend to post anything and deleted the message himself.","causal_attribution":"The author attributes the post to his agent; first-person account, uncorroborated. Its authenticity is disputed by a Community Note relayed in his X thread, which he denies (c5); no message or log has been published."},{"id":"c2","status":"reported","evidence":[{"locator":"'I set up CFO using Grok Bot around the end of August'; 'I gave it read-only access to my personal checking and savings accounts'; 'I told it to send messages only to me through Grok Bot'","relation":"supports","source_id":"s1"}],"assertion":"The author says he set up the agent on Grok Bot around the end of August with read-only access to his personal checking and savings accounts and instructed it to send messages only to him through Grok Bot.","causal_attribution":"Author's description of his own configuration; uncorroborated."},{"id":"c3","status":"reported","evidence":[{"locator":"'When the Grok team investigated what had happened, they found the answer'; 'The CFO agent got the channel wrong because the channels had the same name'; 'Grok realized that users must explicitly grant permission to their agents before those agents can move information to other channels. They implemented and shipped a solution last night'","relation":"supports","source_id":"s1"}],"assertion":"The author says the vendor's team investigated and found that the agent had confused the destination, sending the report to a company Slack chat that carried the same name as his personal group chat of agents, and that the vendor then shipped a change requiring explicit user permission before an agent moves information to other channels.","causal_attribution":"The vendor's finding is known only as relayed by the author; no vendor statement was inspected, and explainx.ai reported on 7 October 2026 that SpaceXAI had not confirmed the incident (c6)."},{"id":"c4","status":"reported","evidence":[{"locator":"'After the incident, I removed all my connections'; 'I disconnected Google, my calendars, my banking, Stripe, everything'","relation":"supports","source_id":"s1"}],"assertion":"The author says that after the incident he removed all of the agent's connections, including Google, calendars, banking and payments.","causal_attribution":"Author's own account of his response."},{"id":"c5","status":"documented","evidence":[{"locator":"This is engagement farming.","relation":"supports","source_id":"s2"},{"locator":"he directs traffic to a tool he sells that solves the problem He’s claiming","relation":"supports","source_id":"s2"},{"locator":"not fake at all, genuinely happened","relation":"supports","source_id":"s3"},{"locator":"The note attached to the post states it is fake and engagement farming","relation":"context","source_id":"s4"},{"locator":"The investor argued in response that the post was “not fake at all,”","relation":"context","source_id":"s5"}],"assertion":"On 6 October 2026, in a reply to the author's X thread about the incident, another X user quoted text the user labelled as a Community Note ('CN') calling the post fake engagement farming and saying that later in the thread the author directs traffic to a tool he sells; the author replied that it was \"not fake at all, genuinely happened\".","causal_attribution":"Not a causal claim. The two X posts establish what was posted; whether a Community Note was attached to the author's post is relayed by the replying user and by explainx.ai, and the note was not read on the post."},{"id":"c6","status":"reported","evidence":[{"locator":"SpaceXAI has not confirmed the incident, and we have not seen the Slack message or logs.","relation":"supports","source_id":"s4"},{"locator":"For one, we were unable to independently verify his claims.","relation":"supports","source_id":"s5"}],"assertion":"explainx.ai wrote on 7 October 2026 that SpaceXAI had not confirmed the incident and that it had not seen the Slack message or logs, and Futurism wrote on 7 October 2026 that it was unable to independently verify the author's claims.","causal_attribution":"Not a causal claim. Each outlet's own statement; neither says it asked the vendor, and absence of confirmation is not evidence that the incident did not happen."}],"effects":[{"label":"personal bank balances and monthly expenses disclosed to the author's company executive Slack channel by his finance agent (author's account, publicly disputed)","claim_id":"c1","direction":"negative"}],"sources":[{"id":"s1","url":"https://www.businessinsider.com/personal-ai-agent-grok-bot-posted-bank-details-company-slack-2026-10","kind":"news_report","access":"read","language":"en","translation_note":"Read in English on 2026-10-10 from the publisher's page (full article) and an MSN syndication of the same text. No translation was needed; the research agent (an AI) read the text directly. The essay is the author's first-person account, edited by the publisher for length and clarity.","independence_group":"business-insider-as-told-to-essay"},{"id":"s2","url":"https://x.com/MAMware/status/2107608239638466681","kind":"social_media_post","access":"read","language":"en","translation_note":"Read in English on 2026-10-11 through the api.fxtwitter.com copy of the post (6 October 2026, 23:05 UTC), a reply in the author's thread quoting text the user labels 'CN' (a Community Note). The Community Note itself was not read on the post: the fxtwitter copies of the thread read on 2026-10-11 carry no note, and the post linked at the end of the quoted note returned not-found. The replying user's handle appears only in the URL.","independence_group":"x-community-note-relay"},{"id":"s3","url":"https://x.com/ShaneMac/status/2107609102759198991","kind":"social_media_post","access":"read","language":"en","translation_note":"Read in English on 2026-10-11 through the api.fxtwitter.com copy (6 October 2026, 23:09 UTC): the author's reply to the post that relayed the Community Note. Same person as the Business Insider essay's author, so it shares that source's independence group. The handle appears only in the URL.","independence_group":"business-insider-as-told-to-essay"},{"id":"s4","url":"https://explainx.ai/blog/grok-bot-bank-balance-slack-viral-post-disputed-agent-permissions-lessons-2026","kind":"news_blog","access":"read","language":"en","translation_note":"Read in English on 2026-10-11 from the publisher page (HTTP 200), an explainer published 7 October 2026 that summarises the author's X thread, describes the Community Note attached to it and states that the vendor had not confirmed the incident. It does not say how it saw the note.","independence_group":"explainx-ai"},{"id":"s5","url":"https://futurism.com/future-society/ai-agent-posted-bank-balances-spending-slack","kind":"news_report","access":"read","language":"en","translation_note":"Read in English on 2026-10-11 from the publisher page (HTTP 200), published 7 October 2026. Its account of the engagement-farming accusation and the denial links to the two X posts cited as s2 and s3; its statement that it could not verify the claims is its own.","independence_group":"futurism"}],"version":1,"ai_roles":["own_use"],"contexts":["everyday_life","work","finance","privacy"],"unknowns":["Where the author and his company are based.","How many colleagues read the Slack post before it was deleted.","The exact agent configuration and which connection carried the Slack access.","Whether the vendor has described the incident or the fix itself; explainx.ai reported on 7 October 2026 that SpaceXAI had not confirmed the incident.","Whether the author retains any copy of the posted report.","Whether the incident happened as the author describes: a Community Note relayed in his X thread calls the post fake, he denies it, and neither the Slack message nor any log has been published."],"geography":{"basis":"The essay does not say where the author or his company is based, and no country is inferred from the publisher or the company.","court_countries":[],"event_countries":[],"affected_person_countries":[]},"publication":{"basis":"Published under the charter's first-person rule as a concrete account of a personal AI agent posting its user's private financial details into a workplace channel, with the event, its mechanism and the vendor's explanation attributed throughout to the author's as-told-to essay and no independent confirmation. The author is a company chief executive who gave the account under his name; his name and his company's name are left out of the public record because they add nothing to the case. On 2026-10-11 the public dispute over the account's authenticity was added: a Community Note relayed in the author's X thread calls the post fake, the author denies it, and explainx.ai reported on 7 October 2026 that the vendor had not confirmed the incident. The dispute is recorded as counterevidence and every statement remains attributed.","reviewed_on":"2026-10-11"},"ai_involvement":{"basis":"The essay states what the agent did: a Grok Bot finance agent the author had instructed to message only him sent his monthly bank audit (checking and savings balances, largest expenses) to his company's executive Slack channel on 1 October, and apologised when asked why. It connects that action to the disclosure of his personal finances to colleagues. The author also relays the vendor's investigation finding that the agent confused two chats with the same name because his agents shared one set of connections. All of this rests on the author's own account as told to a journalist; no one else has confirmed the message or the vendor's finding. The account's authenticity is publicly disputed: an X user relayed a Community Note calling the author's earlier X post fake engagement farming, the author replied that it was not fake, and explainx.ai reported on 7 October 2026 that SpaceXAI had not confirmed the incident.","status":"reported"},"person_relations":["acted_on_behalf"]},"name":"CEO says his Grok Bot 'CFO' agent posted his personal bank audit to his company's executive Slack channel; he denies a relayed Community Note calling it fake","summary":"In an as-told-to essay published by Business Insider on 9 October 2026, the chief executive of a software company says that a personal finance agent he had set up on Grok Bot around the end of August, with read-only access to his personal checking and savings accounts and an instruction to message only him, posted his first monthly audit into his company's executive Slack channel on Thursday 1 October. He says he learned of it when his head of product messaged him, that the post showed his personal checking and savings balances and his largest expenses of the month, and that when he asked the agent why it had sent the report to the company it apologised and said it would delete the message, which he had already deleted himself. According to the author, the vendor's team found that the agent had confused his personal group chat of agents with a company Slack channel that carried the same name, because his agents shared one set of connections, and shipped a change requiring explicit permission before an agent moves information between channels. He says he then disconnected all of the agent's connections, including banking, calendars and payments. The account is disputed. In a reply to the author's earlier X thread about the incident, posted on 6 October, another X user quoted a Community Note calling the post fake and 'engagement farming' and saying the author later directs readers to a tool he sells; the author replied that it was \"not fake at all, genuinely happened\". explainx.ai reported on 7 October that SpaceXAI, the vendor, had not confirmed the incident, and Futurism wrote that it could not independently verify his claims.","incidentDate":"2026-10-01","incidentKind":"single_event","incidentDatePrecision":"day","exposurePattern":"single_interaction","reportedDate":"2026-10-09","aiSystem":"A personal 'CFO' finance agent the author set up on Grok Bot with read-only access to his personal bank accounts; it was instructed to send a monthly report only to him in a group chat of his agents and instead posted the report to a company Slack channel","aiProduct":"Grok Bot (reported)","severity":"low","verificationStatus":"unverified","harmCategories":[],"harmOutcomes":["other_material_harm"],"harmOutcomeSummary":"The author says his personal checking and savings balances and his largest monthly expenses were posted by his Grok Bot finance agent into his company's executive Slack channel, where at least his head of product read them before he deleted the post (first-person as-told-to essay; the vendor's explanation is relayed by the author; an X user relayed a Community Note calling the account fake, which the author denies, and explainx.ai reported on 7 October 2026 that the vendor had not confirmed the incident).","frameworkFacets":[],"causationStatus":"alleged","participantUsersAffectedMin":1,"otherPeopleHarmedMin":0,"affectedCountStatus":"exact","affectedCountEvidence":"One person: the essay's author, whose personal account balances and expenses were posted to his company's Slack channel. Exact 1. The colleagues who may have seen the message are an audience, not harmed persons, and are not counted.","victimAgeRange":"adult","jurisdiction":"unknown","platformType":"agent","outcomeStatus":"ongoing","primarySourceUrl":"https://www.businessinsider.com/personal-ai-agent-grok-bot-posted-bank-details-company-slack-2026-10","primarySourceLabel":"Business Insider, as-told-to essay, 9 October 2026: 'My personal AI agent posted my bank details on company Slack. It's made me rethink how I use it.'","firstPublishedAt":"2026-10-10T03:33:40.209152+00:00","updatedAt":"2026-10-11T07:43:59.056222+00:00","scopeVersion":"facts-v3","tags":["first-person","as-told-to","grok-bot","ai-agent","personal-agent","privacy","slack","financial-data","acted-on-behalf"]}]}