180 incidents on record · 2026 Headlights Incident reports by Ellie Harris · Melbourne
10 new this week Library last updated 30 August 2026
← The incident library
HD-INC-142
Social media and online platforms · West Bank · 2017 · Machine translation error acted on without a human check

Facebook translated a Palestinian man's 'good morning' as 'attack them', and police arrested him

By Ellie Harris · Filed Post and arrest around 15 October 2017

Alleged: Facebook (Meta Platforms) as the translation provider developed or deployed the AI system implicated in this incident. Details are drawn from public reports; parties are presumed innocent of any wrongdoing not established by an official finding.

Facebook translated a Palestinian man's 'good morning' as 'attack them', and police arrested him

What happened

In October 2017, a Palestinian construction worker posted a photo of himself at work with a simple greeting in Arabic that meant “good morning.”

Facebook’s automatic translation got it badly wrong.

Instead of translating the post as a friendly greeting, it reportedly translated it as “attack them” in English and “hurt them” in Hebrew. The difference came down to a single letter in the original Arabic.

Israeli police saw the translated post and arrested the man on suspicion of incitement. According to public reports, no Arabic-speaking officer checked the original post before action was taken. Once investigators realised the translation was incorrect, the man was questioned and released.

Facebook apologised for the mistake and said it would continue improving its translation system.

What an auditable version would have shown

An auditable translation system would make it obvious when a translation had been generated by AI rather than a person. It would keep a record of the original text, the translated version, and how confident the system was in its translation. For short phrases where a single letter can completely change the meaning, it would flag the translation as uncertain rather than presenting it as fact. Most importantly, it would show that a significant decision was about to be made based on a machine translation that no human had verified.

Where the gap was

The problem wasn’t that the AI made a translation mistake. The problem was that the translation was treated as if it were a verified fact. Machine translation is often least reliable with short phrases, slang and local dialects. Yet there was nothing in the process requiring someone who actually spoke Arabic to read the original message before action was taken. The technology made the first mistake. The process allowed it to become a human one.

What governance should have looked like

If an AI translation is going to influence a decision about a person, it should not be treated as the final answer. The translation should be clearly marked as machine-generated, include an indication of how confident the system is, and require a human fluent in the language to verify the original before any action is taken. A VerificationGate is designed to pause decisions until that human check has happened. A ConductRecord keeps the original text, the AI translation, and a record of who relied on it. Together they make it possible to understand not only that a mistake occurred, but exactly where it entered the process and why nobody caught it. The goal isn’t to stop people using AI translation. It’s to stop a machine’s best guess becoming the basis for a decision about another person’s life.

The reference implementation of VerificationGate and ConductRecord is open source. It lives at github.com/saffronandindia/headlights-oss, Apache 2.0 licensed, free for any company to install. The repository is public now.

Sources

The mailing list

Fresh incident reports every week. One email to match.

We add new incidents to the library regularly, and send a single short email each week with what's new. The library stays free and open; this is just how you keep up with it.

No tracking. Unsubscribe in one click.

The record

An auditable system would have produced a signed, tamper-evident record the moment this happened: what the system did, the version that did it, the basis it acted on, and the action taken, and Facebook (Meta Platforms) as the translation provider could have produced it on demand.

This is the record the system as deployed did not produce in a signed, auditable form.

What this teaches
Capture what happened when it happens
What the system did, the version that did it, the basis it acted on, and the action taken, recorded at the moment, not reconstructed after.
Sign it, so no one has to trust the record-keeper
A tamper-evident entry. Edit it later and the signature breaks. The record does not ask for the benefit of the doubt.
Make it verifiable by anyone
A court, a regulator, a customer's lawyer can check the record themselves, without taking the company, or us, at our word.

Headlights summarises publicly reported AI incidents. All summaries are independently written, attributed to their original sources, and intended for research and educational purposes. Allegations are identified as such until established through official findings.

This report is based on the sources listed above and reflects information available at the time of review; later developments may not be captured. Where a person is described as charged with or alleged to have done something, that allegation is unproven unless a conviction or a court or regulatory finding is stated. Headlights publishes journalism and commentary, not legal advice.

Want to write back?

Direct to my inbox.

ellie@useheadlights.com →