Skip to main content
Back to the takedown index

Safe-Inet / Insorg VPN takedown

December 2020, Criminal hosting and proxies

Extended pass entry, last reviewed August 21, 2026

What was taken down?

VPN service infrastructure and associated domains taken offline.

See what happened

What happened to the people?

No individual outcomes are recorded against this entry.
Group accounted for: Not established

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

A multinational coalition took offline Safe-Inet, a VPN service heavily marketed to and used by cybercriminals to anonymize attacks.

Date
December 2020
Target
Safe-Inet (also known as Insorg), bulletproof vpn service
Activity
Criminal hosting and proxies
Operational lead
Not established
Partners
Europol[1]
Jurisdiction
Not established
Outcome
VPN service infrastructure and associated domains taken offline.
Status
Completed
Legal mechanism
Coordinated national judicial/search-and-seizure authority.
Group accounted for
Not established

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: Not established

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]
    Popular VPN used by ransomware gangs taken down

    Europol, December 22, 2020, Source grade P2

    Establishes the multinational takedown of Safe-Inet/Insorg VPN infrastructure.

    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.