Binance Hit by Record-Breaking $6.3bn Hack in Largest Crypto Heist
an organization was hit by a ransomware attack from BYOD that didn't stop at encryption -- data was copied out too.
an organization was hit by a ransomware attack from BYOD that didn't stop at encryption -- data was copied out too.
The group has claimed 11 million customers were affected, though that figure comes from the attackers' own claim and is not independently verified.
The affected organization is now dealing with both a system outage and stolen data sitting outside its control.
Anyone whose data the affected organization holds is potentially affected, not just the affected organization itself.
The threat didn't stop at locking files; stolen data sitting on a leak site is a second, separate form of pressure that a restored backup can't fix.
The attack has been attributed to BYOD, a named ransomware operation.
The affected organization has not paid the ransom.
Not paying denies the group this specific payout, but it doesn't undo whatever was already exfiltrated before the decision was made.
Review backup integrity and restoration speed now, before an incident, since recovery speed is what separates a bad week from a bad year.
Your own incident-response and business-continuity plan is only as good as the longest outage it was actually built for, not just a short disruption.
What happened
an organization was hit by a ransomware attack from BYOD that didn't stop at encryption -- data was copied out too.
The group has claimed 11 million customers were affected, though that figure comes from the attackers' own claim and is not independently verified.
What changed
The affected organization is now dealing with both a system outage and stolen data sitting outside its control.
Who is affected
Anyone whose data the affected organization holds is potentially affected, not just the affected organization itself.
Why it matters
The threat didn't stop at locking files; stolen data sitting on a leak site is a second, separate form of pressure that a restored backup can't fix.
Technical details
The attack has been attributed to BYOD, a named ransomware operation.
Response
The affected organization has not paid the ransom.
Not paying denies the group this specific payout, but it doesn't undo whatever was already exfiltrated before the decision was made.
What security teams should do
Review backup integrity and restoration speed now, before an incident, since recovery speed is what separates a bad week from a bad year.
Your own incident-response and business-continuity plan is only as good as the longest outage it was actually built for, not just a short disruption.