Interpol Red Notice Gone Wrong: The Case of Refugee Footballer Hakeem al-Araibi

A refugee footballer with Australian protection status landed in Bangkok for his honeymoon in November 2018. Immigration flagged his passport—a Red Notice had been active for three weeks, issued by the country he fled. Within hours, he was in a Bangkok remand facility, despite Interpol regulations prohibiting alerts against recognized refugees.

Hakeem al-Araibi’s case exposed systemic failures in both Interpol’s data-processing controls and Australia’s duty of care to refugees traveling abroad. A Red Notice—cancelled within 24 hours of refugee-status confirmation—had been loaded onto Australia’s Central Movement Alert List without screening for protection status, then shared with Thai border authorities. The result: 77 days in custody. The case demonstrates how bureaucratic failures can override legal protections, leaving refugees vulnerable to arrest in third countries even when their protection status is formally recognized.

Interpol Red Notice – an international alert issued by Interpol at the request of a member country’s National Central Bureau, requesting law enforcement worldwide to locate and provisionally arrest a person pending extradition, surrender, or similar legal proceedings (Interpol Rules on the Processing of Data, Article 82).

TL;DR: In November 2018, Bahrain used an Interpol Red Notice to trap Hakeem al-Araibi — a recognized Australian refugee — at Bangkok airport, triggering his provisional arrest and 77 days in custody. Interpol cancelled the notice within 24 hours of learning his refugee status, but Thailand’s independent international extradition process kept him imprisoned. Three Australian agencies failed to cross-check his protection visa against the alert. Only global diplomatic pressure and FIFA’s threatened sanctions forced Bahrain to withdraw its extradition request. The case exposed a critical gap: a cancelled Red Notice does not end detention when bilateral extradition proceedings are already underway. Challenges can be filed with the CCF, but even that doesn’t guarantee immediate release.

Key Takeaways

• Bahrain issued a Red Notice on November 8, 2018, despite al-Araibi holding recognized refugee status in Australia—a direct breach of Interpol’s Rules on the Processing of Data.
• The Australian Department of Home Affairs took nearly three weeks to inform the Australian Federal Police of al-Araibi’s refugee status after receiving the Red Notice alert on November 9, 2018. During this window, border systems remained flagged.
• Interpol cancelled the Red Notice within 24 hours of receiving confirmation of refugee status on November 28, 2018, yet al-Araibi remained detained for 77 days—a reminder that cancellation at headquarters doesn’t automatically unlock detention in the arresting country.
• The Australian Border Force loaded the Red Notice onto the Central Movement Alert List 13 days after the AFP alert without notifying the AFP/Interpol office that al-Araibi held a protection visa.
• Al-Araibi filed a negligence claim in the Supreme Court of Victoria in June 2021 against three Australian government agencies for breach of duty of care.

Who Is Hakeem al-Araibi and Why Was He Forced to Flee Bahrain?

Hakeem al-Araibi is a former Bahraini national team footballer who fled Bahrain in 2014 after allegations of torture while in custody. In November 2012, Bahraini authorities arrested him on charges of vandalizing a police station during Arab Spring protests—charges al-Araibi denied, stating he was playing in a televised football match at the time. During detention, he reported severe physical abuse. After his release, harassment from security services continued, leaving him no safe option but departure.

Australia granted him refugee status and a protection visa in 2017. He settled in Melbourne, married, and played for Pascoe Vale FC in Victoria’s semi-professional league. Under the 1951 Refugee Convention, to which both Australia and Bahrain are signatories, a refugee cannot be returned to a country where their life or freedom would be threatened—a principle known as non-refoulement. That protection doesn’t vanish at the airport.

Article 28 of the 1951 Refugee Convention requires states to issue travel documents to recognized refugees. Article 33 prohibits any measures that would expose refugees to danger from their country of origin. When Bahrain subsequently requested a Red Notice, it violated both the explicit rules of international refugee protection and the underlying principle that states cannot use international mechanisms to hunt down people they’ve already persecuted.

What protection does refugee status provide under international law?

Refugee status under the 1951 Refugee Convention provides protection against refoulement—forced return to a country where a person faces persecution. Once recognized, refugees receive travel documents allowing international movement while maintaining protection. The Convention prohibits signatory states from penalizing refugees for illegal entry or presence, provided they came directly from a territory where their life or freedom was threatened and present themselves promptly to authorities.

Interpol’s own rules mirror this protection. Article 2 of the Interpol Statute requires the organization to respect the Universal Declaration of Human Rights and prohibits any intervention in matters of a political, military, religious, or racial character. The Rules on the Processing of Data explicitly forbid Red Notices against recognized refugees requested by the country from which they fled—precisely because such notices weaponize international law enforcement infrastructure to pursue political dissidents or persecuted minorities.

What Is an Interpol Red Notice and How Did One Get Issued Against a Protected Refugee?

A Red Notice is not an international arrest warrant. It is a request to law enforcement worldwide to locate and provisionally arrest a person pending extradition proceedings. Each country retains discretion to honor or ignore the notice. Before publication, Interpol’s General Secretariat in Lyon reviews every notice to ensure compliance with Article 2 of the Interpol Statute and the Rules on the Processing of Data.

Bahrain issued the Red Notice on November 8, 2018, requesting al-Araibi’s arrest for the 2012 vandalism charge. The notice should never have been published. Interpol’s RPD explicitly prohibits alerts against refugees from their country of origin. The request bypassed or ignored the mandatory compliance screening. For 20 days, it remained active—long enough to trap a traveling refugee on the other side of the world.

The breach was institutional. Australia’s Department of Home Affairs received notification of the Red Notice on November 9, 2018—one day after its issuance—yet took nearly three weeks to inform the Australian Federal Police that al-Araibi held a protection visa. The Australian Border Force, in turn, loaded the notice onto the Central Movement Alert List 13 days after receiving the AFP alert, without flagging the refugee status. When al-Araibi and his wife boarded a flight to Bangkok on November 27, 2018, Thai authorities were waiting.

Can Interpol issue Red Notices for refugees?

No. Article 3 of the Interpol Rules on the Processing of Data prohibits processing data when it concerns a refugee from the country requesting the alert. The rule prevents member states from exploiting Interpol mechanisms to pursue individuals who have fled persecution. Once refugee status is confirmed, the General Secretariat is required to refuse or delete any notice that violates this rule.

In al-Araibi’s case, Interpol cancelled the Red Notice within 24 hours of receiving formal confirmation from Australia on November 28, 2018, at 3:03 pm. The speed of cancellation underscores how clear-cut the violation was. Yet the notice had already been active for 20 days, and al-Araibi was already in custody. Interpol’s failure was not in the cancellation—it acted promptly—but in the initial screening and in Australia’s catastrophic delay in communicating his protection status.

What are the rules governing Interpol Red Notices?

Interpol Red Notices are governed by the Interpol Statute and the Rules on the Processing of Data, revised most recently in 2019. Article 2 of the Statute requires strict neutrality and respect for human rights. Article 82 of the RPD defines a Red Notice as a request to locate and provisionally arrest pending extradition. Article 3 prohibits data processing for political, military, religious, or racial purposes, or when the subject is a refugee from the requesting country.

Before publication, the General Secretariat’s Notices and Diffusions Task Force reviews each request for compliance. National Central Bureaus submit requests through secure channels, and Interpol applies a multi-layer review. Challenges can be filed through the Commission for the Control of Interpol’s Files (CCF), an independent body that adjudicates complaints. The CCF has authority to order deletion, correction, or annotation of data when it finds a breach of Interpol’s rules.

The system failed in al-Araibi’s case because the review either missed the refugee status or proceeded on incomplete information from Bahrain. Australia’s delay in alerting Interpol to the protection status compounded this initial failure, allowing the notice to remain active during the critical window when al-Araibi was traveling.

How Did Australian Authorities Fail Hakeem al-Araibi at the Border?

A cascade of administrative failures. On November 9, 2018, the Australian Federal Police received notification that Bahrain had requested a Red Notice. The AFP’s Interpol office should have immediately cross-referenced al-Araibi’s name with immigration records to check for protection status. It didn’t. The Department of Home Affairs, which holds refugee status data, did not confirm al-Araibi’s protection visa to the AFP until November 28, 2018—nearly three weeks later.

On November 22, 2018, the Australian Border Force loaded the Red Notice onto the Central Movement Alert List, a database that flags travelers at immigration checkpoints. The Border Force did not notify the AFP or Interpol that al-Araibi held a protection visa. When al-Araibi checked in for his flight to Bangkok on November 27, 2018, Thai authorities received advance passenger information showing an active Red Notice. Arrest followed at Suvarnabhumi Airport.

Australia’s duty of care to refugees includes safeguarding their ability to travel without exposure to the country they fled. The three-week delay and the failure to annotate the protection status on the alert list breached that duty. Had the Border Force flagged the refugee status when loading the notice, or had Home Affairs acted within 24 hours of receiving the alert, al-Araibi’s travel would have been restricted or the notice would have been cancelled before departure.

What went wrong with Australia’s duty of care to refugees?

Australia’s failure was structural. Three agencies—Department of Home Affairs, Australian Federal Police, and Australian Border Force—each held part of the information needed to prevent the arrest, but communication between them failed at every checkpoint. Home Affairs possessed refugee status data but did not cross-check it against Red Notice alerts in real time. The AFP received the alert but lacked immediate access to immigration databases. The Border Force loaded the alert without verifying protection status.

The Australian government has since implemented procedural reforms, including automated cross-referencing of Red Notice alerts with refugee and protection visa databases. The reforms aim to prevent future cases where recognized refugees are inadvertently flagged for arrest. At the time of al-Araibi’s detention, no such system existed, and the manual coordination required to prevent the error failed repeatedly.

Al-Araibi’s lawyers later argued that the government owed a duty of care to notify refugees of Red Notices and to prevent their travel to countries likely to honor arrest requests. The negligence claim, filed in June 2021 in the Supreme Court of Victoria, sought damages for the 77-day detention and the psychological harm caused by the threat of extradition to Bahrain.

Why Did al-Araibi Spend 77 Days in a Bangkok Prison Despite Interpol Cancelling the Notice?

The Red Notice was cancelled on November 29, 2018, within 24 hours of Interpol receiving confirmation of refugee status from Australia. Al-Araibi remained in detention because Thailand’s domestic legal process had already begun. On December 12, 2018, a Thai court ordered his detention extended by 60 to 90 days to allow immigration authorities to process Bahrain’s formal extradition request.

Under the 2007 extradition treaty between Thailand and Bahrain, Bahrain submitted a full extradition request with supporting documentation. Thai law requires courts to evaluate whether the request meets treaty requirements—specifically, whether the charged offense is extraditable and whether the evidence is sufficient to proceed. The cancellation of the Red Notice removed the Interpol alert but did not automatically void the bilateral extradition request. Here’s the critical gap: Interpol and bilateral extradition operate on separate tracks.

Thailand faced conflicting pressure. Bahrain demanded extradition based on the 2012 criminal conviction. Australia, human rights organizations, and the international football community demanded release. FIFA threatened to suspend Thailand from international competition if al-Araibi was extradited, citing torture risk and breaches of refugee protections. The Thai attorney general’s office ultimately decided not to proceed, and Bahrain withdrew its extradition request on February 11, 2019. Al-Araibi walked free the same day.

What this reveals: even when Interpol acts swiftly to correct a wrongful notice, domestic extradition proceedings continue independently. Refugees detained on cancelled Red Notices remain vulnerable until the requesting country withdraws its formal extradition demand or the detaining country refuses it. The system contains no automatic release mechanism.

How long was Hakeem al-Araibi detained in Thailand?

Al-Araibi was detained for exactly 77 days, from November 27, 2018, to February 11, 2019. Bangkok Remand Prison held him—a facility designed for pretrial detainees. Overcrowding. Limited legal access. Constant uncertainty about whether Thailand would extradite him. His lawyers filed multiple petitions for provisional release on bail. All denied by Thai courts while the extradition decision remained pending.

The timeline shows how these cases actually unfold. Arrest within hours of arrival. First court hearing on December 12, 2018 extended detention by two months. Interpol’s cancellation came early—within the first week—but had no immediate effect on the Thai court’s authority to hold him while evaluating the extradition request. Only sustained diplomatic pressure, public campaigns, and Bahrain’s eventual withdrawal secured his release. For most detainees without his profile, that pressure never materializes.

Takeaway: The Red Notice was active for 21 days, but detention lasted 77 days—nearly four times longer. Cancellation of the notice stopped new arrests but did not immediately free al-Araibi from the extradition process already underway. Legal teams working on similar cases must address both the Interpol alert and the bilateral extradition request simultaneously. Treating these as separate problems means leaving your client in custody while one track resolves.

What International Pressure Finally Secured al-Araibi’s Release?

Diplomatic intervention came from multiple fronts. Australian Prime Minister Scott Morrison personally contacted Thai Prime Minister Prayut Chan-o-cha, requesting al-Araibi’s release on humanitarian grounds. The Australian embassy in Bangkok provided consular support and legal assistance throughout the detention. FIFA issued a public statement calling for immediate release and threatened sanctions against Thailand’s football federation if extradition proceeded.

Social media amplified the pressure. The #SaveHakeem campaign mobilized international football players, coaches, and fans. Didier Drogba posted appeals. Jamie Vardy spoke out. Human Rights Watch and Amnesty International issued reports documenting al-Araibi’s torture allegations and the risk of further persecution if returned to Bahrain. Global media framed the case as a test of Thailand’s commitment to refugee protection and rule of law.

On February 11, 2019, Bahrain announced it would withdraw the extradition request, citing desire to maintain relations with Thailand. The Thai attorney general’s office confirmed it would not proceed. Al-Araibi walked out of Bangkok Remand Prison later that day. Within 48 hours he was back in Melbourne. The withdrawal was strategic for both sides—Bahrain faced reputational damage, and Thailand risked FIFA sanctions that would have isolated its national team.

What matters here: international attention can override bilateral legal processes. But success is not guaranteed. Al-Araibi benefited from his profile as a footballer, FIFA’s involvement, and Australia’s diplomatic leverage. Refugees without these advantages often remain detained for months or years while extradition proceedings drag on. Resources focused on asset recovery and legal enforcement can sometimes assist in parallel civil claims to secure release or compensation, though jurisdiction and available remedies vary significantly.

What Legal Action Did al-Araibi Take Against the Australian Government?

In June 2021, al-Araibi filed a negligence claim in the Supreme Court of Victoria against three Australian government agencies: the Department of Home Affairs, the Australian Federal Police, and the Australian Border Force. The claim alleged breach of duty of care, arguing that the government owed a responsibility to protect recognized refugees from arrest and extradition by countries they fled. The failures stacked: no cross-check of refugee status against the Red Notice. A three-week delay in notifying Interpol. Loading the alert onto the border watchlist without annotation. All contributed to his 77-day detention.

The claim sought damages for psychological harm, loss of liberty, and trauma from facing potential extradition and torture. Al-Araibi’s legal team argued that the failures were not isolated errors but systemic deficiencies in how Australia manages Red Notices concerning protected persons. The case raised a fundamental question: to what extent does government liability arise when administrative failures expose refugees to danger from their countries of origin? If courts recognize this duty, future cases may be prevented. If they reject it, refugees traveling abroad remain exposed to similar bureaucratic failures.

As of 2026, the public outcome has not been fully disclosed. The case prompted internal reviews within Australian government agencies and contributed to procedural reforms, including automated cross-referencing systems to prevent similar incidents. Whether the government ultimately accepted liability or settled remains under discussion in legal circles.

Did Hakeem al-Araibi sue the Australian government?

Yes. Al-Araibi filed a negligence lawsuit in June 2021, alleging that Australian government agencies breached their duty of care by failing to protect his refugee status when the Red Notice was issued. The claim named the Department of Home Affairs, Australian Federal Police, and Australian Border Force as defendants. His argument: the government’s internal communication failures and the decision to share the Red Notice with Thai authorities exposed him to detention and extradition risk, violating Australia’s obligations under the 1951 Refugee Convention.

The case is significant for refugee protection policy globally. Outcome matters enormously. A finding of duty of care would require real-time screening of Red Notices against refugee databases—a procedural safeguard that could prevent similar incidents. A ruling against him would leave refugees traveling abroad vulnerable to the same bureaucratic gaps that entrapped al-Araibi.

This article is published by an independent law firm for informational purposes only and does not represent or claim affiliation with any government body, international organization, or official authority.