MACGRP retweeted
If Phantom is still showing a warning on stakepoint.app from Saturday's registrar incident, use stakepoint.io
Same platform, same contracts, same wallet. Fresh domain, no flags, nothing to click through.
stakepoint.app remains our main site and the warning will clear as Phantom completes its review.
(Teams please share with your communities) and thank you for your patience!
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.
MACGRP retweeted
🚨 Community Alert: Our system has detected a potential frontend attack targeting @flapdotsh and @Kintsu:
• flap[.]sh
• kintsu[.]xyz
Please refrain from signing transactions and avoid interactions with these dApps until the issue is resolved.
MACGRP retweeted
In addition to our earlier alert, the same attack has now been identified on additional sites. These are actively serving the Step Drainer:
• stonkfun[.]xyz
• pickle[.]finance
• echelon[.]market
• origami[.]finance
• fluxbeam[.]xyz
• stakepoint[.]app
• supswap[.]xyz
• longbow[.]cash
• shprd[.]finance
• apexdefi[.]xyz
We’re actively investigating and gathering more data.
MACGRP retweeted
JUST IN: 🇺🇸 President Trump says he is looking into the $6.3 billion Binance crypto hack.
MACGRP retweeted
Saw a few discussions about size of hack, why impact to bitcoin price is small, etc. 👇
$6.3 billion is the biggest in USD terms, but not in BTC terms. MtGox was 650,000 BTC!
Other important numbers to consider:
% of bitcoin (in relation to BTC total supply), ie, market impact. MtGox is big there again at 5%+.
Number of users impacted, and % of user assets impacted. MtGox (the largest CEX at the time) and FTX (not small) were all near 100% of users and their asseets.
Most important: Who is impacted? Does the platform cover it all? (only one victim), as in recent two CEX cases and Binance.
Obviously, still a major disaster for the industry, Binance (and me). It hurts, but we survive.
Most importantly, we protect our users.
(image from @MatthewRoszak)
I am utterly perplexed by:
Where the fuck is Richard?
You and @cz_binance been on the ball but him lack of or no show. Maybe its time for a change. Real change and not a stamp.
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.
MACGRP retweeted
**Service Update**
Deposits remain unaffected and continue to operate as normal.
Our team is currently working on enhancements to the withdrawal service and related address controls. We expect to begin resume withdrawal services in the next 48 hours.
We will continue to share updates through official Binance channels as progress is made.
MACGRP retweeted
Thank you for the collective support from the community.💛
We are currently conducting a security scan to ensure the safety of funds within the platform. 🙏
User funds SAFU.
Binance's initial investigation suggests that the security incident may involve a compromised DevOps engineer’s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. We have found no evidence of any wallet private key leak. We will share a detailed technical post-mortem once the investigation is complete and the facts are fully verified.
The estimated total impact sits at around $6.3B. We have worked with blockchain partners to freeze affected assets, with ~$3 billion frozen on-chain so far.
Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe. We will also publish an updated Proof of Reserves once the remediation is complete.
As an immediate precaution, Binance has:
- temporarily suspended deposits and withdrawals while security checks are completed;
- revoked the affected address authorisation;
- engaged law enforcement and blockchain intelligence partners to trace and recover funds.
Our teams are working around the clock to resolve this issue safely and thoroughly. We are working closely with our law enforcement partners to confirm the identity of these criminals and bring them to justice.
Please rely only on official Binance channels for updates. Please feel free to contact Binance Customer Support if you have any further questions.
binance.com/en/support/annou…
The Arbitrum Security Council has taken emergency action to rescue the 74,559,805 ARB and 8,425 ETH being held in the address on Arbitrum One that is identified as connected to the Binance exploit. The Security Council acted by weighing its commitment to the security and integrity of the Arbitrum community and Arbitrum governance without impacting any Arbitrum users or applications.
After significant technical diligence and deliberation, the Security Council identified and executed a technical approach to move funds to safety without affecting any other chain state or other Arbitrum users.
As of October 30, 2026 time, the funds have been successfully transferred to an intermediary frozen wallet. They are no longer accessible to the address that originally held the funds, and can only be moved by further action of the Security Council or a vote of Arbitrum DAO governance, which will be coordinated with relevant parties.
MACGRP retweeted
‼️ UPDATE ON THE BINANCE HACK:
Whoever emptied a Binance hot wallet had 50 authorisations signed with that wallet's own private key, on-chain data shows.
Under Ethereum's EIP-7702, an authorisation is a signed permission that lets a wallet hand control of itself to code.
Each one works only for the wallet's next transaction number, its nonce. Binance's wallet was still sending transactions, so that number kept moving.
The sender didn't know which number would be live, so they packed all 50 into one transaction, Blockaid says. One matched.
That one installed a sweeper contract on the wallet. Blockaid found that only the Tornado Cash-funded sender can operate it.
Minutes later it emptied the wallet of $1.6B in USDT, 167,464 ETH and 60+ other tokens.
Only that key, or the system that holds it, can produce those signatures. How the sender got them is unknown.
Across Ethereum, Bitcoin and Tron, at least $5.57B left Binance-linked wallets.
Binance says user funds are "completely safe" but has not explained how.
We are working non-stop to resolve this issue. Binance will cover all losses.
As a precaution, all deposits and withdrawals are temporarily suspended while our team conducts security checks, freezes funds, and works with law enforcement.
We are working around the clock and will share a full post-mortem once the investigation is complete. Please rely only on official Binance channels for updates.
This is an industry-wide effort, and we are grateful to partners across the ecosystem who have moved quickly to help freeze affected assets.
We will continue to share verified updates through official Binance channels. User funds are safe.
MACGRP retweeted
Tether froze more than 1.567B USDT related to a potential Binance exchange hack.
Protecting the industry and our partners is our main priority.
Stay safe everyone.
Track the $5B Binance hack through this custom Arkham entity by @emmettgallic
arkm.com/explorer/entity/21a…
Earlier today, public reports indicated that Binance was impacted by a security incident. Blockchain analysis showed that PAXG tokens held on the Binance platform were moved to the suspected attacker’s address.
After confirming the reports with its own blockchain investigation, Paxos froze 1,906.67 PAXG tokens in wallet: 0x5227f603C1eE34CE3C06eFe6477003BDfCCB2f8c
Paxos systems have not been impacted by this incident. Reserves for PAXG, PYUSD and USDG remain fully intact and redemptions continue to operate normally.
This is a rapidly evolving situation. We will provide updates as appropriate as details come to light. As always, Paxos will work closely with law enforcement and regulators.
































