{"id":61085,"date":"2023-09-14T18:55:22","date_gmt":"2023-09-14T22:55:22","guid":{"rendered":"https:\/\/ifintechworld.com\/markets\/crypto\/crypto-theft-from-fortress-trust-traced-back-to-phishing-attack-on-cloud-vendor\/"},"modified":"2023-09-14T18:55:25","modified_gmt":"2023-09-14T22:55:25","slug":"crypto-theft-from-fortress-trust-traced-back-to-phishing-attack-on-cloud-vendor","status":"publish","type":"post","link":"https:\/\/ifintechworld.com\/?p=61085","title":{"rendered":"Crypto Theft from Fortress Trust Traced Back to Phishing Attack on Cloud Vendor"},"content":{"rendered":"
\n

Fortress Trust’s recent disclosure of a cryptocurrency theft totaling nearly $15 million has shed light on a complex situation involving a third-party vendor and a phishing attack.<\/p>\n

The vendor has now been identified as ReTool, a reputable San Francisco-based company serving Fortune 500 clients. Retool constructed the portal that allowed several Fortress clients to manage their cryptocurrency funds.<\/p>\n

The theft, attributed to a phishing attack, prompted Fortress to speed up discussions with blockchain tech firm Ripple for its acquisition. Retool has confirmed that it fell victim to a phishing attack affecting 27 of its customers, but didn’t directly reference Fortress in its statement.<\/p>\n

The attack targeted a specific group of crypto-oriented customers, but those who configured Retool’s software as recommended by the company remained unaffected.<\/p>\n

\u201cAlthough an attacker had access to Retool cloud, there was nothing they could do to affect on-premise customers,\u201d emphasized Retool. \u201cIt\u2019s worth noting that the vast majority of our crypto and larger customers in particular use Retool on-premise.\u201d<\/p>\n

Although $15 million is a substantial sum, it represents a small fraction of Fortress’s overall assets under management, which total billions of dollars. Ripple has made a $15 million down payment to help Fortress reimburse affected customers, as part of their ongoing acquisition deal.<\/p>\n

The Timeline<\/h2>\n

According to a Ripple spokesperson, Fortress initially covered most affected customers, and Ripple stepped in to ensure all customers \u2013 particularly one large customer \u2013 were made whole within a week.<\/p>\n

Fortress initially disclosed the security breach on September 7, without naming the compromised third-party vendor. Ripple, which had already been a minority investor in Fortress, announced its intent to acquire the custodian the following day. The incident expedited the takeover talks, according to Ripple, as they swiftly acted to ensure customer protection.<\/p>\n

BitGo and Fireblocks, the wallet providers used by Fortress, clarified that their systems were not breached. BitGo’s CEO Mike Belshe emphasized that their company was not involved in the breach and criticized Fortress’s handling of the situation, as they did not immediately disclose all details.<\/p>\n

<\/oembed><\/figure>\n

Fortress CEO Scott Purcell claimed that Belshe was informed of all events regarding the security breach from the moment they had occurred.<\/p>\n

Swan Bitcoin, a brokerage firm utilizing Fortress’ BitGo wallets for client funds, confirmed<\/a> that the coins stored in those wallets remained secure throughout the incident.<\/p>\n

The Nevada Financial Institutions Division, responsible for overseeing Fortress, was informed of the incident on September 1, according to an agency spokesperson.
\u00a0<\/p>\n<\/p><\/div>\n