Skip to main content
Back to the takedown index

iSpoof takedown

November 2022, Fraud and stolen data
Led by Metropolitan Police Service

Extended pass entry, last reviewed August 21, 2026

What was taken down?

Platform infrastructure seized; service taken offline.

See what happened

What happened to the people?

Officials reported 142 apprehended.
Group accounted for: Partial

See people and accountability

Did it stay down?

Not established in the public record. No later activity is recorded against this entry.

See what happened afterward

London's Metropolitan Police led a takedown of iSpoof, a caller-ID spoofing-as-a-service platform used to facilitate telephone fraud; Europol reported around 142 arrests connected to the operation.

Date
November 2022
Target
iSpoof, spoofing as a service
Activity
Fraud and stolen data
Operational lead
Met Police
Partners
Europol[1]
Jurisdiction
Not established
Outcome
Platform infrastructure seized; service taken offline.
Status
Completed
Legal mechanism
UK judicial search/seizure authority.
Group accounted for
Partial

No individual is named against this entry in the cited record. That is a gap in what has been published rather than a finding that nobody was involved.

Group accounted for: Partial

The cited record does not say how large the group was or whether everyone involved has been identified.

See the organizations and roles behind this action

Not established in the public record. No later activity is recorded against this entry.

Numbered markers throughout this entry link to the source that supports the claim beside them.

Official sources

  1. [1]
    iSpoof: fraud-enabling platform taken down and 142 arrested worldwide

    Europol, November 24, 2022, Source grade P2

    Establishes the Metropolitan Police-led takedown and the 142-arrest figure.

    No address recorded for this source. Publisher, title, and date are given so it can be retrieved from the publisher.

Coverage note. Added from deep-research aggregation pass. Not independently re-verified source-by-source to the same standard as the original 38-incident core; source_quality capped at S2/P2 pending a dedicated verification pass.