On-chain sleuth Specter said in a post on X that the time range covered by the stolen data suggests the breach may have occurred as early as April, and no later than early May. Specter said the party involved stayed silent until recently, around the same time Trezor disclosed its own data leak. He also said some users had already received phishing attacks at the time and suffered asset losses, while the party involved neither gave users a warning nor issued a risk notice. Instead, according to Specter, it denied that a data leak had taken place. The post focuses on the timing implied by the compromised dataset and on the response of the party involved, rather than adding further technical details about the breach.
ChainCatcher reported that on-chain investigator Specter said in a post on X that the time span covered by the stolen data suggests the leak may have taken place as early as April, and no later than early May.
Specter said the party involved remained silent until recently, at roughly the same time Trezor announced its own data leak.
He also said some users had already been targeted by phishing attacks and suffered asset losses at the time, but the party involved did not act transparently, did not warn users or issue risk alerts, and instead denied that a data leak had occurred.
This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan. Disclaimer:
The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.
Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.
