Account

Posts of CRYPTO ROAST

newest first

#2006Text
Views1,915−43%vs avg
Forwards0
Reactions70
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
1 h411
13 h1,337
26 h1,915
  1. After 1 hour411
  2. After 24 hours1,915
  3. Total to date1,915
#2005Text
Views3,766+13%vs avg
Forwards1
Reactions177
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
3 h644
5 h822
15 h1,411
27 h2,064
80 h3,766
  1. After 6 hours822
  2. After 24 hours2,064
  3. Total to date3,766
#2004Text
Views3,581+7%vs avg
Forwards2
Reactions221
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
1 h353
13 h1,280
26 h1,909
74 h3,581
  1. After 1 hour353
  2. After 24 hours1,909
  3. Total to date3,581
#2003Text
Views3,729+12%vs avg
Forwards0
Reactions199
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
3 h693
15 h1,446
27 h1,993
76 h3,729
  1. After 24 hours1,993
  2. Total to date3,729
#2002Text
Views3,658+9%vs avg
Forwards0
Reactions171
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
2 h655
14 h1,410
26 h1,964
46 h2,592
75 h3,658
  1. After 24 hours1,964
  2. Total to date3,658
#2001Text

🔤 UPD: North Korea Denies Involvement in $6.3B Binance Hack 🟠The Binance hack saga just turned into an international political dispute. North Korea has reportedly denied any involvement in the massive exchange breach, calling the US accusations a political provocation. 🟠According to the latest reports, Kim Yo Jong, sister of North Korean leader Kim Jong Un, stated that Pyongyang is closely monitoring the situation surrounding Binance. 🟠The North Korean government reportedly dismissed the hacking allegations as “FAKE”, accusing Washington of using the incident to make politically motivated claims against the country. 🟠Previously, the FBI reportedly attributed the attack to TraderTraitor, a North Korean-linked hacking group, alleging that approximately $6.3 BILLION had been stolen from Binance. 🟠That’s significantly higher than the initial $3.5B+ estimates. The discrepancy remains unresolved, and the full scale of the attack has yet to be independently established. 🟠Meanwhile, Binance has reportedly replenished approximately 95% of the stolen assets and resumed withdrawals across multiple networks. But the question of who actually orchestrated the attack remains disputed. 🟠And here’s the thing: a government denial doesn’t disprove technical attribution, just as an accusation alone doesn’t establish every detail of an attack. The evidence behind the FBI’s claims matters far more than the political statements. 👉 Billions allegedly stolen, Washington pointing at Pyongyang, and North Korea calling it fake. This is no longer just a crypto security story.

Open in Telegram
Views3,611+8%vs avg
Forwards3
Reactions164
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
5 h783
17 h1,846
29 h2,316
61 h3,197
78 h3,611
  1. After 6 hours783
  2. After 24 hours2,316
  3. Total to date3,611
#2000Text

🔤 UPD: Binance Restores Withdrawals After Massive Hack 🟠Remember the reported $3.5B+ Binance hack? The situation has developed rapidly. Binance is now restoring withdrawals, covering stolen assets from its own reserves, and dealing with billions in customer outflows. 🟠According to the latest updates, Binance has already replenished approximately 95% of the stolen assets. The exchange says it will absorb the financial losses rather than pass them on to customers. Balances of $BTC, $ETH, $USDT, $BNB, $SOL, $USDC, $XRP, $USD1, $RLUSD and $ZEC are reportedly fully backed. 🟠Withdrawals are also coming back online. What started with Ethereum and BNB Smart Chain has expanded to 15 networks, including Bitcoin, Solana, Tron, TON, Base, Arbitrum and Optimism. Remaining assets are being enabled gradually as security checks continue. 🟠But customers aren’t exactly rushing to celebrate. Binance reportedly recorded $3.6 BILLION in net outflows after withdrawals reopened. Meanwhile, another $500M in USDT moved from exchange wallets, although Binance representatives described the transfers as internal hot-wallet operations. 🟠The alleged attacker has also been busy. Reports suggest more than 130 EVM tokens were sold for approximately $279M. In one particularly ridiculous transaction, the attacker reportedly tried to dump $5M worth of $PROM into an almost empty liquidity pool and received just $71. Apparently, even hackers need to learn about slippage. 🟠Meanwhile, reports attribute the attack to North Korea’s TraderTraitor group, with claims that the total theft exceeded $6B. That figure differs significantly from earlier estimates and still requires independent verification. Rumors about a Binance engineer and a supposed North Korean spy have also circulated, but ZachXBT has not confirmed that story. 🟠The exchange is expected to publish updated cryptographic proof of customer asset backing by November 3. Until then, the key questions remain how much was actually stolen, how much has been recovered, and whether Binance can fully restore customer confidence. 👉 Replacing stolen crypto is one thing. Rebuilding trust after billions in withdrawals is a completely different challenge.

Open in Telegram
Views3,819+14%vs avg
Forwards1
Reactions212
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
1 h421
13 h1,369
25 h1,962
73 h3,819
  1. After 1 hour421
  2. After 24 hours1,962
  3. Total to date3,819
#1999Text
Views3,602+8%vs avg
Forwards1
Reactions207
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
2 h594
14 h1,420
65 h3,098
75 h3,602
  1. Total to date3,602
#1998Text
Views3,318−1%vs avg
Forwards0
Reactions168
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
12 h1,139
36 h2,386
73 h3,318
  1. Total to date3,318
#1997Text
Views3,374+1%vs avg
Forwards1
Reactions143
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
9 h988
13 h1,275
32 h2,024
68 h3,374
  1. After 24 hours2,024
  2. Total to date3,374
#1996Text
Views3,543+6%vs avg
Forwards1
Reactions153
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
12 h1,370
36 h2,608
40 h2,757
71 h3,543
  1. Total to date3,543
#1995Textedited
Views4,167+25%vs avg
Forwards2
Reactions231
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
2 h616
13 h1,282
25 h1,802
33 h2,170
73 h3,384
  1. After 24 hours1,802
  2. Total to date4,167
#1994Text
Views3,379+1%vs avg
Forwards0
Reactions145
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
9 h1,085
31 h2,327
51 h2,963
67 h3,379
  1. After 24 hours2,327
  2. Total to date3,379
#1993Text

🔤 UPD: Ledger Was Warned About Hardware Implants Months Ago 🟠Remember the suspected $90M Ledger supply-chain attack? The story just got worse. According to new reports, Ledger had received warnings about modified hardware wallets months before the October scandal. 🟠At least two people reportedly contacted Ledger about suspicious devices as early as December 2025. Then, on March 4, 2026, security researcher Joe Grand informed the company about a malicious hardware implant discovered inside a Ledger Nano X purchased through Lazada in Thailand. 🟠Ledger reportedly acknowledged the report and promised an internal investigation. But despite receiving information about potentially compromised devices, the company did not issue a public warning to customers. 🟠Fast-forward to October. Multiple Ledger devices have reportedly been discovered with hidden hardware implants, while investigators are examining thefts approaching $90M. The exact connection between the modified devices and the stolen funds remains unconfirmed. 🟠Former Mt. Gox CEO Mark Karpelès, who reportedly discovered a suspicious component inside his own Ledger, argues that the growing number of cases and sophistication of the implants should have prompted action long before the scandal became public. 🟠When journalists asked Ledger why customers hadn’t been warned earlier, the company reportedly declined to provide a direct explanation, referring instead to its existing public statements on X. 🟠And that’s the uncomfortable part. Knowing about a potential supply-chain threat isn’t the same as proving a widespread compromise. But when customers are trusting your hardware with potentially millions of dollars, deciding when to warn them becomes a security decision of its own. 👉 A compromised wallet is a security failure. Ignoring early warning signs could turn it into a much bigger one.

Open in Telegram
Views3,793+13%vs avg
Forwards2
Reactions199
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
6 h942
15 h1,472
27 h2,059
30 h2,162
74 h3,793
  1. After 6 hours942
  2. After 24 hours2,059
  3. Total to date3,793
#1992Text
Views3,734+12%vs avg
Forwards2
Reactions199
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
11 h1,390
30 h2,480
54 h3,270
75 h3,734
  1. After 24 hours2,480
  2. Total to date3,734
#1991Text
Views3,809+14%vs avg
Forwards5
Reactions258
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
3 h797
7 h1,269
34 h2,641
51 h3,219
71 h3,809
  1. After 6 hours1,269
  2. Total to date3,809
#1990Text
Views4,038+21%vs avg
Forwards0
Reactions228
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
7 h1,044
16 h1,682
27 h2,635
71 h4,038
  1. After 6 hours1,044
  2. After 24 hours2,635
  3. Total to date4,038
#1989Text
Views4,173+25%vs avg
Forwards0
Reactions293
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
8 h1,383
36 h3,105
44 h3,468
70 h4,173
  1. Total to date4,173
#1988Text
Views4,356+30%vs avg
Forwards2
Reactions354
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h250
5 h1,039
10 h1,347
32 h2,677
38 h2,957
67 h4,356
  1. After 1 hour250
  2. After 6 hours1,039
  3. Total to date4,356
#1987Text
Views3,113−7%vs avg
Forwards2
Reactions210
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
1 h256
24 h1,587
59 h2,624
72 h3,113
  1. After 1 hour256
  2. After 24 hours1,587
  3. Total to date3,113
#1986Text
Views3,063−8%vs avg
Forwards0
Reactions136
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
1 h257
66 h3,063
  1. After 1 hour257
  2. Total to date3,063
#1985Text
Views3,239−3%vs avg
Forwards0
Reactions159
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h186
26 h1,786
71 h3,239
  1. After 1 hour186
  2. After 24 hours1,786
  3. Total to date3,239
#1984Text
Views2,245−33%vs avg
Forwards1
Reactions5
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h217
7 h1,018
37 h2,245
  1. After 1 hour217
  2. After 6 hours1,018
  3. Total to date2,245
#1983Text
Views2,465−26%vs avg
Forwards0
Reactions5
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
1 h305
21 h1,508
50 h2,465
  1. After 1 hour305
  2. After 24 hours1,508
  3. Total to date2,465
#1982Text
Views2,582−23%vs avg
Forwards3
Reactions4
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h253
10 h1,146
45 h2,582
  1. After 1 hour253
  2. Total to date2,582
#1981Text

🔤 UPD: The $352M Bitget Hack Started Almost a Month Earlier 🟠Remember the $351.6M Bitget hack? SlowMist’s investigation suggests the actual operation didn’t begin on September 24. The first traces of malicious activity reportedly appeared as early as August 31. 🟠According to SlowMist, the attacker exploited a zero-day vulnerability in a third-party security service, gaining access to its database. Malicious activity was later identified on two additional nodes — suggesting the attackers were already establishing their foothold weeks before the money moved. 🟠Then on September 25, the attacker reportedly compromised another third-party security service using an employee account and began uploading malicious files. The attackers had also prepared a tool specifically designed for Bitget’s internal systems. 🟠That tool could allegedly forge risk-control parameters, automatically generate withdrawal requests and execute them. Once the theft began, assets were withdrawn across multiple blockchains for almost three hours. 🟠SlowMist is still investigating exactly how the attackers moved between the compromised systems. But the timeline makes one thing clear: this wasn’t a quick wallet exploit. It appears to have been a multi-stage operation prepared weeks in advance. 🟠Meanwhile, Bitget is gradually restoring withdrawals. USDT withdrawals are now available on Ethereum, BSC, Solana and Tron, while BTC and ETH withdrawals had already been reopened. 👉 The $352M disappeared in hours. The attack behind it may have been running for almost a month.

Open in Telegram
Views3,135−6%vs avg
Forwards4
Reactions61
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
20 h1,589
34 h2,319
68 h3,135
  1. After 24 hours1,589
  2. Total to date3,135
#1980Text

🔤 UPD: $50M From the Bitget Hack Hit NEAR Intents 🟠Remember the $351.6M Bitget hack? Some of the stolen crypto is now testing an uncomfortable question for DeFi: what exactly does “permissionless” mean when a protocol can still freeze your funds? 🟠More than $50M linked to the Bitget hack was reportedly routed toward NEAR Intents. Its SHIELD system blocked most of those attempts during the quote stage, while another $503K was frozen during execution. Around $166K still made it through. 🟠And that triggered a debate. NEAR Intents describes itself as permissionless, but its architecture allows specific governance addresses to block accounts and even pause swaps and withdrawals entirely. 🟠NEAR Intents responded with a simple argument: “permissionless does not mean neutral.” In other words, anyone may be able to access the protocol — but that doesn’t necessarily mean the protocol has to process every transaction. 🟠Compare that with THORChain, which reportedly refused to selectively block hacker-linked funds after the same Bitget incident, pointing specifically to its permissionless architecture. 🟠Important distinction: NEAR Intents is a separate protocol built on top of NEAR. These controls exist at the Intents layer and do not mean the NEAR blockchain itself can selectively freeze funds. 👉 The Bitget hack is turning into more than a $352M security incident. Now it’s exposing where different DeFi protocols draw the line between permissionless infrastructure and intervention.

Open in Telegram
Views2,978−11%vs avg
Forwards1
Reactions6
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
1 h263
58 h2,978
  1. After 1 hour263
  2. Total to date2,978
#1979Text
Views1,029−69%vs avg
Forwards0
Reactions—
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h147
11 h1,029
  1. After 1 hour147
  2. Total to date1,029
#1978Text
Views2,451−27%vs avg
Forwards2
Reactions5
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
1 h363
16 h1,475
37 h2,451
  1. After 1 hour363
  2. After 24 hours1,475
  3. Total to date2,451