Skip to main content
Back to overview
High

Tosaf Hacked by Handala Ransomware Group

Tosaf, an industrial giant with over 5,000 employees and 60 offices worldwide, was named on the Handala ransomware data-leak site on February 2, 2025.

Key points

  • Claimed by Handala ransomware group.
  • Full control of Tosaf's systems.
  • Initiated a full lockdown of entry points to facilities.

Connected intelligence

Signal brief

Follow the organization, likely method and potential impact to explore connected Shadow Tier intelligence.

02

Likely method

Ransomware

Threat source not confirmed

03

Potential impact

Potential operational disruption

Availability

Published
Feb 2, 2025
Updated
Jul 1, 2026
Confidence
High
Evidence
3 sources

Structured assessment

Signal analysis

This analysis groups the signal by industry, likely incident action and impacted security area. It helps compare this signal with other published signals without treating the labels as final determinations.

Threat source

Threat source not confirmed

Watch ransomware, endpoint compromise and business interruption exposure.

Business impact

Potential operational disruption
Impact area
Availability

Mentioned entities

TosafTosaf HackedHandala Ransomware Group TosafHandalaThe HandalaTosafClaimedFullInitiated

Quick context

Questions about this signal

What happened in this signal?

Tosaf, an industrial giant with over 5,000 employees and 60 offices worldwide, was named on the Handala ransomware data-leak site on February 2, 2025. The Handala group claimed to have successfully breached and taken full control of Tosaf's systems, initiating a full lockdown of entry points and exfiltrating data.

When was this signal reported?

Shadow Tier lists Feb 2, 2025 as the signal date.

Which organization is connected to this signal?

Tosaf is the organization connected to this public signal.

Explore Tosaf
Which attack pattern is relevant?

This signal is connected to current ransomware incidents based on its reported incident context.

Explore current ransomware incidents