Napi kripto hírek, elemzések, oktatás és közösség technikai, pszichológiai és fundamentális alapon. A kereskedés kockázatos, fektess be felelősségteljesen!
Budapest, Magyarország
Joined March 2018
- Tweets21K
- Following308
- Followers5.4K
- Likes18.3K
CryptoFalka Hungary retweeted
Strategy has acquired 1,036 $BTC and repurchased $188M of $STRC. As of 11/8/26, we hold 850,364 BTC and $4.9B of USD Assets. $MSTR strategy.com/press/strategy-…
CryptoFalka Hungary retweeted
JUST IN: 68.2% of 2026 midterm winners have been pro-crypto, according to Stand With Crypto 🇺🇸
245 pro-crypto candidates have been elected so far! 👀
CryptoFalka Hungary retweeted
Strategy has acquired 811 $BTC and repurchased $208M of $STRC. As of 11/1/26, we hold 849,327 BTC and $4.9B of USD Assets. $MSTR strategy.com/press/strategy-…
CryptoFalka Hungary retweeted
JUST IN: 44% of the $6.43 billion stolen from Binance has now been frozen or seized, according to Elliptic 👀
CryptoFalka Hungary retweeted
12 hours after withdrawals resumed: 2.1% net outflow, with most occurring in the first couple of hours. Over $1 billion in flow, too.
98% choose to stay!
Trust isn’t earned by what you say in good times. It’s earned by what you do in hard times.
Thank you for your trust! 🙏🙏🙏🙏
Binance began restoring withdrawals in phases at 06:00 UTC on November 1, 2026. By 12:36 UTC, withdrawals had resumed for all 15 networks and assets in the initial phase. After an initial spike, withdrawal volumes have declined and are stabilising as expected, while deposit volumes have remained substantial.
Between 06:00 and 15:30 UTC on November 1, we processed $4.649 billion in withdrawals and $1.01 billion in deposits, resulting in a net outflow of approximately $3.64 billion. This represents 2.1% of our $171 billion in total assets under management (AUM), based on the latest available Proof of Reserves (PoR) data as of October 28, 2026. A new PoR snapshot was taken at 00:00 UTC on October 31, and zero-knowledge proof (ZKP) computation began. The updated report is expected to be available on our PoR website tomorrow.
Our team continues testing rigorously the remaining networks and assets. We know how important safe and reliable access to your funds is and will share details of the next phase as soon as we can. Rest assured that market conditions are stable.
Thank you for your patience and continued support.
CryptoFalka Hungary retweeted
October in a nutshell:
- PHP got hacked
- Railway got hacked
- OpenCode got hacked
- Binance got hacked
- Polymarket got hacked
- GitHub Actions got hacked
- SoftBank got hacked
- Cursor marketplace got hacked
- Coinbase vendor got hacked
- Fireworks AI got hacked
- LiteLLM got hacked
- Capcom got hacked
- npm packages got hacked
- TiDB Cloud got hacked
- Warp's vendor got hacked
happy cybersecurity awareness month
CryptoFalka Hungary retweeted
BINANCE HACKER LOSES NEARLY $5 MILLION IN BOTCHED UNISWAP TRADE
A wallet linked to the Binance hacker dumped 908,793 PROM tokens, valued at approximately $5 million, into a nearly empty Uniswap V2 liquidity pool.
The hacker received just 0.0316 ETH, worth $71, effectively wiping out the tokens’ entire quoted value in a single trade.
It wasn’t the hacker’s first costly liquidation.
Earlier, the attacker sold 134.1 million FUN tokens, worth roughly $1.17 million at pre-sale prices, for just $250,000 in ETH.
The hacker’s rush to convert stolen altcoins into ETH has resulted in extreme slippage across illiquid markets.
CryptoFalka Hungary retweeted
🚨 BREAKING: BINANCE ENGINEER HAD ROMANTIC RELATIONSHIP WITH NORTH KOREAN SPY BEFORE $6.3B HACK
New, unverified allegations claim that a Binance DevOps engineer was romantically involved with a North Korean operative and left their laptop unattended on the day of the attack.
The hack has previously been linked to a compromised engineer's laptop, while North Korean hackers have been implicated in the wider breach.
The romantic relationship and unattended-laptop claims are being attributed to ZachXBT online, but his original statement has not been independently verified.
Readers added context they thought people might want to know
Claims that a Binance DevOps engineer had a romantic relationship with a North Korean spy and left their laptop unattended are unverified false rumors falsely attributed to ZachXBT. No such details appear in his posts or official reports.
cryptotimes.io/2026/11/01/fac…
en.wikipedia.org/wiki/2026_Bina…
x.com/zachxbt/status…
CryptoFalka Hungary retweeted
BREAKING: The FBI announces that North Korea was behind the $6.3 billion hack of Binance, now the largest hack in history.
North Korean hackers were previously accused by the FBI of some of the biggest crypto hacks.
This includes the $1.5 billion Bybit attack last year and the 2022 theft of $620 million in cryptocurrency.
North Korea is now responsible for both the first and second largest crypto hacks in history.
CryptoFalka Hungary retweeted
Binance began restoring withdrawals in phases at 06:00 UTC on November 1, 2026. By 12:36 UTC, withdrawals had resumed for all 15 networks and assets in the initial phase. After an initial spike, withdrawal volumes have declined and are stabilising as expected, while deposit volumes have remained substantial.
Between 06:00 and 15:30 UTC on November 1, we processed $4.649 billion in withdrawals and $1.01 billion in deposits, resulting in a net outflow of approximately $3.64 billion. This represents 2.1% of our $171 billion in total assets under management (AUM), based on the latest available Proof of Reserves (PoR) data as of October 28, 2026. A new PoR snapshot was taken at 00:00 UTC on October 31, and zero-knowledge proof (ZKP) computation began. The updated report is expected to be available on our PoR website tomorrow.
Our team continues testing rigorously the remaining networks and assets. We know how important safe and reliable access to your funds is and will share details of the next phase as soon as we can. Rest assured that market conditions are stable.
Thank you for your patience and continued support.
CryptoFalka Hungary retweeted
The FBI is releasing information advising the Democratic People's Republic of Korea (North Korea) was responsible for the theft of more than $6 billion USD in virtual assets from cryptocurrency exchange, Binance, on or about October 29, 2026. The FBI refers to this specific North Korean malicious cyber activity as "TraderTraitor."
The FBI, together with partners at the USSS and IRS-CI, has observed TraderTraitor actors converting stolen assets primarily into Ethereum (ETH). It is expected these assets will then be further laundered by converting them using DeFi and instant swap services as they prepare them for further laundering stages.
How You Can Help:
FBI, USSS, and IRS-CI are urging private sector entities including THORNode operators, RPC node operators, instant exchanges, DeFi services, blockchain analytics firms, and other virtual asset service providers to block transactions with or derived from addresses TraderTraitor actors are using to launder these stolen assets.
A list of addresses associated with this activity is available here: fbi.gov/investigate/cyber/al…
ALT FBI public service announcement with Department of Justice seal in the background on a gold gradient.
CryptoFalka Hungary retweeted
People are dumb.
FTX was maybe 8B.
But that was $8B when BTC was at $20K.
$8B at $80K BTC is a completely different story.
Its 4X less impactful in relative terms.
So if we got a dip to $15.5K back then, roughly 20%, we should see around a 5% dip now, assuming the same proportional impact.
That puts BTC around 76K.
Add a bit more FUD, and $73K ish makes sense.
I know its not 8B but just going off that thought.
Hilarious how people are calling for 30% dip🤣
CryptoFalka Hungary retweeted
This single transaction (`0xad99264d...`) is the exact moment Binance 14 got hijacked.
Because Binance 14 is a high-frequency hot wallet with a constantly moving nonce, Lazarus couldn't just sign one delegation — it would expire before landing on-chain.
Instead, they pre-signed a shotgun blast of 50 consecutive EIP-7702 authorizations and stuffed them into a single type-4 tx. 49 missed. One hit the exact live nonce.
Cost to hijack the largest exchange hot wallet on earth: $14.58 in gas.
The craziest detail in the Binance 14 takeover tx (`0xad99264d...`): a 3-minute-24-second gap between the EIP-7702 delegation landing on-chain (block 26300753) and the main sweep executing costed $0.92.
For 17 straight blocks, Binance's main hot wallet had its bytecode pointing straight at a North Korean sweeper contract (`0x63e8...6fae`), and zero automated circuit breakers tripped.
They shotgunned 50 nonces for $14.58, waited 3.5 minutes in plain sight, then emptied the vault.
Best guess? They were not prepared for this kind of hijacking.
Draining $370 million in native ETH and 63 separate ERC-20 tokens in a single atomic transaction.
Total gas cost? $0.92.
- Zero `approve` calls—executing straight `transfer()` inside the hot wallet's own context.
- `staticcall` + `continue` error isolation so a single blacklisted token doesn't brick the whole $6B batch.
- Leaves exactly 1 ETH behind so hot wallet queues don't error out early.
- All executed in one block for less than a buck.
State-sponsored engineering makes retail smart contract optimization look like amateur hour. Lazarus wrote cleaner, more gas-efficient routing code in their sweeper contract than 99% of DeFi protocols on CoinMarketCap.
Breathtaking efficiency.
CryptoFalka Hungary retweeted
HOLY SHIT 🤯
CZ Binance is now indirectly hinting at dumping $1 Billion in $SPCX shares after Elon Musk trolled him.
CryptoFalka Hungary retweeted
Reading the reconstructed bytecode of the Binance EIP-7702 sweeper (`0x63e8...6fae`) is wild.
This wasn't a generic drainer. It was custom-engineered for Binance 14's architecture:
- Leaves exactly 1 ether behind (`bal - 1 ether`) when sweeping ETH so Binance's automated hot wallet queue wouldn't error on gas and trip alarms.
- Uses raw `staticcall` + `continue` loops with custom error codes (`SweepItemFailed`) so one bricked or blacklisted ERC-20 wouldn't revert the $6B batch.
- Includes a custom `callExecute` function to impersonate Binance 14 as controller of an external vault holding $823M in USDC.
They leave a comment: "robberies could be prevented if getaway cars were slower."
You can't fully blame EIP-7702, but it sped up the attack. Without 7702, draining 64 tokens plus an external $823M vault from a live exchange hot wallet meant fighting moving nonces across 70+ transactions. Defense systems would've killed it after tx #3.
With 7702, Lazarus sprayed 50 consecutive nonces in one type-4 payload, turned an EOA into a custom proxy, and atomically swept billions in a single block.
Ethereum core devs built the ultimate getaway car. Surgical state-sponsored engineering.
This could be etched onchain:
`if (bal > 1 ether) { to.call{value: bal - 1 ether}(""); }`
The Binance $5.6B drain is a masterclass in modern EVM exploitation.
It wasn't a complex logic bug. It was an EIP-7702 delegation hijack:
1. Setup: Attacker funds 0x7c86 via Tornado Cash, deploys a sweep contract (0x63e8), and runs three live dry-runs on external wallets.
2. Execution: Attacker submits an EIP-7702 batch with 50 pre-signed authorizations (nonce n to n+49) to hit Binance 14's moving nonce window.
3. One authorization hits. Instantly, Binance 14 (an EOA) is reprogrammed to run the attacker's contract bytecode.
4. Execution looks totally organic: Binance 14 sweeps itself clean. Internal threshold alerts don't trigger because, from the nodes' perspective, the hot wallet is just executing its own transaction.
5. Binance 16 immediately auto-refills 28,000 ETH due to automated treasury rebalance scripts, feeding the exploit loop.
The cold truth: you cannot forge an EIP-7702 delegation list.
For this to execute, the attacker already held the raw private key or unconstrained signing access to Binance 14's HSM/KMS.
But hey, 5.64 billion drained across ETH, BTC, and Tron. 2.54 billion frozen by Tether, Circle, Ripple, and World Liberty within hours.
Code is law until the stablecoin admin keys log in.
Binance got bailed out by the very centralized choke points the cypherpunks warned you about.
Hardware wallets leak your home address.
Centralized exchanges leak the keys to the kingdom.
Self-custody on native, non-delegated chains remains the only honest baseline.
At least you know what to avoid.
Readers added context they thought people might want to know
The quoted comment appears only in an AI-reconstructed source (explicitly labeled not original) uploaded to explorers; no source comments exist in deployed bytecode, and core features match independent decompilations/on-chain data.
etherscan.io/address/0x63e8…
gist.wavey.info/Ta3FgAxastgj42…
x.com/thearsondragon…
CryptoFalka Hungary retweeted
In 2023, after news of the $4 billion fine, Gulf, our partner in Thailand, asked: “do you need help with cash liquidity?” We didn’t, but I appreciated the gesture.
Today: “know you can cover, but we are here if needed.”
Strong partners show in tough times. 🙏
Official Statement Regarding Recent News on Binance Security Incident
In light of recent news regarding a cybersecurity incident involving Binance, Gulf Binance Co., Ltd. would like to confirm that customer digital assets on Binance TH remain completely safe. The Cold Wallets of Binance TH are strictly segregated from those of Binance, as Binance TH operates as an independent legal entity with its own dedicated digital asset custody system.
As a proactive precautionary measure, we would like to inform you that digital asset deposits and withdrawals are temporarily suspended while our expert team conducts a thorough security check. All other services on the platform continue to operate as normal, and we will resume deposit and withdrawal operations as soon as the verification process is completed.
The security of our customers' digital assets remains our highest priority. We remain fully committed to maintaining strict security standards to ensure absolute confidence among all our clients.
We sincerely apologize for any inconvenience caused.
CryptoFalka Hungary retweeted
Binance has begun recovering affected assets for users and continues to work with law enforcement, issuers, blockchain intelligence firms and industry partners to trace, freeze and recover additional funds.
The company has already publicly committed to cover losses through company funds in the prior announcement.
Binance has already reserved over $6.34B of company funds to cover this incident. $5B of these funds are already held in the exact token assets that were impacted. We are completing the purchase of the remaining amount by buying token assets through market channels and OTC channels. We are doing this to match the format of the remaining token assets and address any asset shortfalls. This step can take longer because some tokens may have low liquidity and OTC settlement also takes time. We will share more progress as soon as we can.
These figures do not include frozen or protected assets, which remain subject to ongoing recovery and verification. Currently, $3bn has been frozen, with thanks to our industry partners. We are working with partners and law enforcement to recover the frozen assets.We will continue to use company resources to cover confirmed shortfall and will provide further verified updates as recovery efforts progress. Ultimately, all user funds will be verified publicly through our Proof of Reserves.
We will weather this storm. Thank you for the support.
CryptoFalka Hungary retweeted
I want to speak to you directly about what happened.
Bottom line - your money is safe, and we're covering every loss.
Our initial investigation suggests this security incident may have started with a compromised DevOps engineer's laptop. That gave an attacker access to a service container, where they submitted unauthorized withdrawal transactions.
To be clear: the attacker did not simply use one engineer's permissions, and this was not a single "one-click" action. It involved a more complex attack process. Our investigation has not attributed responsibility to any individual.
So far, we have found no evidence of any wallet private key leak.
We'll share a detailed technical post-mortem once the investigation is complete and every fact is verified - and publish an updated Proof of Reserves once remediation is complete.
What you need to know:
• Your funds are safe
• Binance will cover all losses from the SAFU fund and company funds
• Estimated total impact: ~$6.3B, with ~$3B frozen on-chain so far, in coordination with our blockchain partners
• No evidence of any wallet private key leak
• Deposits are unaffected and operating as normal
What we've done:
• Temporarily suspended withdrawals while we complete a security revamp of the withdrawal service and its related addresses
• Revoked the affected address authorizations
• Engaged law enforcement and blockchain intelligence partners to trace and recover funds
Our team hasn't stopped. We're working closely with law enforcement to ensure the matter is handled appropriately - and I'll share what I can, as soon as I can.