SafePay

Active
569 victims named on the leak site
14 in the last 30 days
247 in the last 12 months
Nov 2024 first victim we recorded
Sep 14, 2026 most recent victim posted
9 leak sites tracked

Data as of September 14, 2026.

Credential exposure before the attack

20% of SafePay victims whose domain we can identify (114 of 569) had employee credentials leak in the 12 months before SafePay named them as a victim.

We don't know whether any of these credentials were how SafePay gained initial access.

What industries SafePay targets

Sector identified for 368 of 569 victims.

Manufacturing87
Construction49
Healthcare44
Education40
Financial Services26
Logistics26
Non-profit16
Legal13

Where the victims are located

Country identified for 387 of 569 victims.

Germany106
United States100
United Kingdom30
Canada29
Italy19
Spain14
Australia12
Argentina11

Most recent SafePay victims

VictimSectorCountryPosted
Compunnel compunnel.comTechnologyUnited StatesSep 14, 2026
Gruppo Assiprime assiprime.itFinancial ServicesItalySep 9, 2026
Cannon Puntana cannonpuntana.comManufacturingArgentinaSep 9, 2026
Century Maritime Agencies cenmar-manila.comNot identifiedPhilippinesSep 9, 2026
Gayafores gayafores.esManufacturingSpainSep 9, 2026
GSN Gestión gsngestion.esReal EstateSpainSep 9, 2026
HBPro hbpro.ptTechnologyPortugalSep 9, 2026
McNish Steel mcnishsteel.comConstructionUnited StatesSep 9, 2026
Palmetto Eye Institute palmettoeyeinstitute.comHealthcareUnited StatesSep 9, 2026
Recovery Café recoverycafe.orgNon-profitUnited StatesSep 9, 2026
Municipality of Reichenau an der Rax reichenau.atGovernmentAustriaSep 9, 2026
Air Liquide Korea airliquide.krHealthcareSouth KoreaAug 26, 2026
La Ge Gè Pesca lagegepesca.itNot identifiedItalyAug 25, 2026
Formatgeria Granja Rinya granjarinya.comNot identifiedSpainAug 17, 2026
Aoyama Zaisan Networks azn.co.jpFinancial ServicesJapanAug 4, 2026
CPU Softwarehouse cpu-ag.comFinancial ServicesGermanyAug 4, 2026
Hanan Transport & Cranes hanan-hov.co.ilLogisticsIsraelAug 4, 2026
Multiaqua multiaqua.comManufacturingUnited StatesAug 4, 2026
Nask Door naskdoorinc.comNot identifiedUnited StatesAug 4, 2026
New Point new-point.itNot identifiedItalyAug 4, 2026

Showing the 20 most recent of 569. Browse recent data breaches for more.

SafePay leak sites

Addresses we've seen SafePay publish victims from. Any .onion address needs the Tor Browser.

  • j3dp6okmaklajrsk6zljl5sfa2vpui7j2w6cwmhmmqhab6frdfbphhid.onion
  • safepaypfxntwixwjrlcscft433ggemlhgkkdupi2ynhtcmvdgubmoyd.onion
  • nz4z6ruzcekriti5cjjiiylzvrmysyqwibxztk6voem4trtx7gstpjid.onion
  • wmgres25e43uwgebctgofo2qe23kf5vqevixiulubpovdglyizfugryd.onion
  • nj5qix45sxnl4h4og6hcgwengg2oqloj3c2rhc6dpwiofx3jbivcs6qd.onion
  • crmbcdcdwoex6dzajbicgzrsuw2t76pomajwdpi2mb2babbfdgcc6xid.onion
  • fcde4o7iquaspdbo5yetwqn3rfueet2zfy3wjosrc5dznyccwbiz6oyd.onion
  • qkzxzeabulbbaevqkoy2ew4nukakbi4etnnkcyo3avhwu7ih7cql4gyd.onion
  • iieavvi4wtiuijas3zw4w54a5n2srnccm2fcb3jcrvbb7ap5tfphw6ad.onion

SafePay questions

Is SafePay still active?

Yes. SafePay posted its most recent victim on September 14, 2026. That's 14 victims in the last 30 days.

How many victims has SafePay claimed?

SafePay has named 569 victims on its leak site since we started tracking it. That counts organizations, not leaked files. A single victim often accounts for thousands of published files. 247 of them were posted in the last 12 months.

When did SafePay first appear?

The first victim we recorded for SafePay was posted on November 21, 2024. That's when the group entered our collection, which isn't necessarily when it started operating.

Which sectors does SafePay target?

Manufacturing accounts for the most victims we can classify, with 87. Construction follows at 49. We could identify a sector for 368 of 569 victims, so treat this as the shape of the targeting rather than a full census.

Has SafePay already got your credentials?

Check whether your employees' logins have leaked on the dark web before they're exploited.

Check your exposure →

Continuous dark web monitoring alerts you when your company's data shows up, whether that's employee credentials or files published after an attack.