Skip to main content
Back to the takedown index

Phobos/8Base ransomware disruption

February 2025, Ransomware

Extended pass entry, last reviewed August 21, 2026

What was taken down?

More than 100 servers disrupted.

See what happened

What happened to the people?

No individual outcomes are recorded against this entry.
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

A multinational coalition disrupted more than 100 servers connected to the Phobos ransomware-as-a-service operation and the affiliated 8Base group, accompanied by arrests.

Date
February 2025
Target
Phobos and 8Base, ransomware group
Activity
Ransomware
Operational lead
Not established
Partners
Europol[1]
Jurisdiction
Not established
Outcome
More than 100 servers disrupted.
Status
Completed
Legal mechanism
Coordinated national judicial/search-and-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]
    Law enforcement disrupts Phobos ransomware and 8Base group

    Europol, February 10, 2025, Source grade P2

    Establishes the disruption of more than 100 servers connected to Phobos/8Base.

    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.