Skip to main content
NOPE
Low reported severity Media Coverage

Portland couple’s private conversation sent to a contact by Alexa

A Portland couple discovered that their Echo had sent a household conversation to a contact. They unplugged their devices. Amazon acknowledged the incident and attributed it to speech being misinterpreted as commands.

AI system
Amazon Alexa
Occurred
May 2018
Reported
24 May 2018
Event location
United States
What the AI did
Acted on the person’s behalf
Reported harm
Other Material Harm
Whose AI use
Their own AI use
Setting
Privacy · Everyday life
Evidence
AI involvement reported · Causal attribution supported · 3 sources, 1 underlying account
3 claims: 3 reported. 3 open questions
People reported harmed
2 people

AI system as recorded: Amazon Alexa on Echo

Reported harm

The couple’s household audio was disclosed to another person without authorization.

Outcome

Unknown

Media Coverage

What remains unknown

  • The exact day is unknown: the 24 May account says two weeks earlier, so only May 2018 is recorded.
  • The recording and device logs were not inspected.
  • Later remedies and any further consequences are unknown.

What the evidence supports

AI involvement: reported. The incident concerns Alexa’s speech recognition and messaging action, with Amazon acknowledging the transmission.

3 claims: 3 reported. What the statuses mean

Reported An Echo sent a Portland couple’s private conversation to a contact without their intended instruction.

Causal attribution. Family account relayed from KIRO, acknowledged by Amazon; logs were not independently inspected.

  • tomsguide.com(opens in new tab) supports · English
    Opening account and paragraph reporting the recipient identifying their household conversation (L628-L632).
Reported Amazon attributed the transmission to a sequence of misinterpreted speech commands.

Causal attribution. Provider explanation, not an independently reproduced technical finding.

  • arstechnica.com(opens in new tab) supports · English
    Update and second update: Amazon’s explanation and its statement that the explanation came from device logs (L90-L92).
Reported The couple unplugged their Alexa devices after discovering the disclosure.

Causal attribution. Reported response to the disclosure.

Sources

3 sources inspected, from 1 underlying account. Sources that repeat one account do not corroborate each other.

How the sources were read, and where the events happened

English article and both updates read directly. Family reporting originates with KIRO; Amazon supplied Ars a statement. Applies to s1.

English article body read directly, excluding related-story cards. Relays KIRO and carries an Amazon statement. Applies to s2.

English NPR transcript read directly. Explicitly credits KIRO; no additional independent witness. Applies to s3.

Event countries: United States. Affected-person countries: United States. Court countries: Unknown.

Tom’s Guide identifies the couple’s home as Portland, Oregon. No court proceeding is cited.

Reviewed for publication 2026-09-25: Concrete adverse experience with a core person relation. Claims remain attributed to their sources. Technical and causal limits are recorded.

People reported harmed in this case

2 people

2 AI participants · 0 other people harmed

The two people whose conversation was disclosed. The recipient is not counted as harmed.

Counted once within this case. The same person may appear in other cases. This count does not establish AI causation.

Cite this case

Compiled per our published methodology: verification statuses, sourcing standards, and corrections process.

APA

NOPE. (2026). Portland couple’s private conversation sent to a contact by Alexa. AI incidents. https://nope.net/incidents/2018-portland-alexa-private-conversation-sent

BibTeX

@misc{2018_portland_alexa_private_conversation_sent,
  title = {Portland couple’s private conversation sent to a contact by Alexa},
  author = {NOPE},
  year = {2026},
  howpublished = {AI incidents},
  url = {https://nope.net/incidents/2018-portland-alexa-private-conversation-sent}
}

Related cases

Medium Grok

Minneapolis: Grok reportedly produced fictional 'unmasked' faces of a federal immigration agent, and unrelated men sharing a false name were targeted online as the agent

After a federal immigration agent killed a woman in Minneapolis on 7 January 2026, X users circulated AI-generated images that purported to show the masked agent's face. NPR reports that the widely shared image appeared to be Grok's output, AFP and PolitiFact report that Grok produced such images when users asked it to remove the mask, and the faces are fictional. Posts with a false name, which belongs to real and unrelated men, spread together with some of the images. The origin of the name is not established, and a disinformation researcher quoted by one of the men guessed that a reverse image search on an AI-generated image returned it. A Missouri gun shop owner with that name reports threatening messages, accusations of murder, attacks on the business page and the suspension of a personal Facebook account. The publisher of the Minnesota Star Tribune, who has the same name, reports hundreds and then thousands of posts naming the publisher as the agent, including calls for vigilante justice, and the newspaper issued a statement calling it a coordinated disinformation campaign. AFP reports that xAI answered its inquiry with an automated reply. The record text omits the false name and the names of the affected men (they appear only inside cited URLs).

Low Grok Bot (reported)

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

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.

Low Meta Muse agent

Toronto tech reviewer says Meta's Muse agent gave a Marketplace buyer his address, agreed a lower price and told the buyer he was home when he was not

Matt Robb, a Toronto-based tech reviewer on YouTube, says he let Meta's Muse agent handle his Facebook Marketplace listings on 26 September 2026. Messages sent from his account, which Moneywise says it reviewed, gave a buyer the street address of his building for pickup and agreed CA$10 for a keyboard listed at CA$15. Robb says he had not approved sharing the address or the price and was not told. According to a recap Muse later sent him, the buyer arrived around 9:15 p.m., Muse's auto-reply told him 'Yep I'm here!' although nobody came down, and he left at 9:38 p.m.; Muse then sent an apology in Robb's voice. Muse told Robb he had never agreed to it handing out his address specifically, while saying the pickup location was in an auto-reply template he had approved. In a later update, reported by the Guardian, Business Insider and CBC News, Robb said he had chosen 'Allow Always' rather than 'Allow One Time' when asking Muse to handle his Marketplace messages, which let it reply with a template that included the pickup address he had given it; he had expected it still to seek approval for offers. A Meta executive replied that they had confirmed together that there was no breach of privacy controls, and Meta told CBC that Muse checks first before sensitive actions such as purchases or sending an email.

Medium Unidentified website-generation tool

Japan: police say two teenagers used generative AI to build a fake payment-service site that took women's details, later used to pay for a hotel and consoles

Shiga prefectural police sent two teenagers' cases to prosecutors on 27 October 2026 on suspicion of violating Japan's unauthorised computer access law. According to the police announcement as reported by the Yomiuri Shimbun and Asahi Broadcasting (ABC), on 13 September 2026 the two, in Tokyo, sent two women the URL of a site made to look like a real payment service, told them they could receive money, and had them enter details such as email addresses and phone numbers. Police say the two used generative AI to make the phishing site, and the Yomiuri reports that one of them, who is believed to have used generative AI to make the fake site, said he did not have the skill to build a site without AI. The same day, police say, they logged into a travel-booking site with one woman's details and paid a Tokyo hotel bill of 182,830 yen; they were later re-arrested over three portable game consoles bought with another woman's account. Police believe they took about 50 people's information, including from other payment services, and charged about 5 million yen. Both admitted the allegations, according to the police. They are not named here.

If you or someone you know is struggling, free and confidential support is available. Find a helpline near you at Signpost.

Back to all incidents