
Pinned Tweet
We compared read-only API keys on 20 exchanges, from each exchange’s own docs.
All 20 offer a key that can see your account and can’t touch it. Some expire if you don’t bind an IP, some never expire, two require an IP from day one.
Sources: truehold.xyz/blog/read-only-…
57
azat retweeted
Rule #1: Don’t send it straight to your everyday wallet.
Use a separate wallet while you assess the risk.
High-risk withdrawal can complicate the history of the wallet you use for savings and daily transactions, making your wallet flagged overall.
azat retweeted
Good evening, Patrón🗝️
Your crypto can be 100% legitimate, and still get frozen.
After the @MEXC headlines, some of my innocent clients ran into a nasty surprise when moving their funds.
Here are 3 rules I wish everyone knew first ⇓
azat retweeted
Top crypto bridges by use case
1/ @AcrossProtocol
Fast ETH & L2 transfers
- Advantage: Low fees, fills often around 2 seconds
- Tradeoff: Large instant transfers depend on relayer liquidity
2/ @RelayProtocol
Fast bridging across many chains
- Advantage: 85+ chains advertised, fast fills, gas sponsorship
- Tradeoff: Fees and liquidity vary significantly by route
3/ @circle (CCTP)
Native asset transfers
- Advantage: 1:1 burn-and-mint for supported assets, including USDC, without market slippage
- Tradeoff: Limited to supported assets/chains; Fast transfers can cost extra
4/ @THORChain
Native BTC and cross-chain swaps
- Advantage: Swap native assets without wrapped tokens or a centralized exchange
- Tradeoff: Liquidity-based slippage, variable fees and network availability
Note: XMR integration is not yet live
5/ @debridge
Fast Solana, TRON & EVM transfers
- Advantage: Fast solver-based execution, quoted rates, broad non-EVM support
- Tradeoff: Route-dependent fees, liquidity and execution limits
6/ @StargateFinance
Stablecoin & ETH liquidity bridging
- Advantage: Shared liquidity architecture, LayerZero integration, flexible routing
- Tradeoff: Fees and execution times vary; batching can introduce delays
7/ @portalbridge_
Broad non-EVM coverage
- Advantage: Access to ecosystems including Solana and Sui
- Tradeoff: Some transfers create wrapped assets instead of native tokens
8/ @mayan
Solana-focused cross-chain execution
- Advantage: Swift solver fills, competitive auctions, transfers in seconds on eligible routes
- Tradeoff: Execution time and pricing depend on route and available solvers
9/ @symbiosis_fi
Cross-chain token swaps, including BTC
- Advantage: One interface for swaps across multiple blockchain ecosystems
- Tradeoff: Multi-step routes may increase fees and execution complexity
10/ @jumperapp
User-friendly Bridge & DEX aggregation
- Advantage: Compares multiple bridges and swaps to find competitive routes
- Tradeoff: Limited to integrated providers and available liquidity
11/ @chainlink (CCIP)
Programmable cross-chain transfers
- Advantage: Security-focused messaging and token-transfer infrastructure
- Tradeoff: Integration requirements and fees depend on the route and configuration
12/ @USDT0_to
Omnichain USDT transfers
- Advantage: 1:1 USDT-backed transfers through LayerZero’s OFT architecture
- Tradeoff: Supported networks, token representations and verification requirements vary
13/ Official / canonical bridges
Direct L1 ↔ L2 transfers
- Advantage: Use the network’s canonical settlement mechanism
- Tradeoff: Some withdrawals, especially optimistic-rollup exits, take approximately 7 days
Remember: The best bridge depends on your exact networks, asset, amount and priorities. Always compare total received, fees, finality and security - not just advertised speed.
🤖 Made with AI
He was asked about tampered devices. Ledger's own lab found implants in wallets sold by a reseller, CryptoBilis, that read the 24 words during setup and sent them out over LTE.
Moving those words to a new device doesn't help. The funds need a new phrase. nitter.cf/Cryptic_Web3/status/21…
🎥 WATCH: Ledger CEO Pascal Gauthier says getting hacked is a matter of “when,” not “if.”
What are your thoughts?
11
304 token unlocks since 2020, each measured against BTC.
The week after an unlock: median -2.3%, about the same as an ordinary week (-2.5%).
Unlocks over 2% of max supply: -8.7% in the week before the date.
truehold.xyz/unlocks/price-i…
8
worse_query went public on Nov 8. Apple's Nov 9 updates don't mention it, so there is no fix to install yet. GitHub already hosts sideloaded tweak apps built on it. A malicious one on a phone with a wallet is the whole attack. nitter.cf/SlowMist_Team/status/2…
🚨 SlowMist TI Alert: iOS sandbox escape 0day PoC “worse_query” disclosed 🚨
A public PoC for a sandbox escape 0day, worse_query, targets iOS 26.0–26.7.2 and iOS 27.2. It is the successor to bad_query. 📱
⚠️ This is a container sandbox escape, not a jailbreak. It breaks the assumption that apps can’t see each other: a malicious app that successfully exploits it can reach system paths and read or modify other apps’ data.
💸 The bug does not steal assets by itself. The real risk starts when a user installs an app from an untrusted source, such as a sideloaded IPA. If a wallet stores its seed phrase, keystore or WebView cache in plaintext locally, a malicious app could read it.
🛡️ Recommendations:
🔸 Don’t install IPAs or apps from unknown sources
🔸 Keep iOS up to date and install Apple’s fix as soon as one is released
🔸 Wallet developers: don’t store sensitive data in plaintext locally
🔸 If you installed an untrusted app on a device holding wallets, treat it as risky and consider moving assets to a new wallet created on a clean device
🔗 github.com/forcequitOS/worse…
7
In December 2022 Ankr lost about $5M when a former team member's planted code leaked its deployer key, which Ankr's own report called a single point of failure.
Today SlowMist says every forged receipt carried a valid signature from the bridge's signer. nitter.cf/Cointelegraph/status/2…
14
In Web3Auth's design, a Google or Apple login wallet has its key split, and one part sits on Web3Auth's nodes until you sign in. Web3Auth paused that service at 21:13 UTC yesterday.
If an app gave you a wallet at Google sign-in, ask who holds that part. nitter.cf/keplrwallet/status/211…
We have received reports of unauthorized transactions on some Keplr accounts created with Google or Apple login. We flagged this to the @Web3Auth team and have been working with them on the investigation since.
Based on our initial assessment: if you created your Keplr wallet with a recovery phrase or a hardware wallet, you are NOT affected.
If you created your Keplr account with Google or Apple login, your account may be affected. While we investigate:
– Do not send new funds to that account.
– Do not re-import or recreate it anywhere.
– Google/Apple login is paused for now.
– Trust updates only from this account. Ignore DMs or links offering “recovery”.
We will share verified details and next steps here as soon as we have them.
45
Chainalysis's Nov 4 update also said logins were down, so customers couldn't yet reset the password it asked them to reset.
If that password is also on an exchange account, change it there first. nitter.cf/WuBlockchain/status/21…
Chainalysis: Names, Usernames, Password Hashes, and Valid Tokens of All Users Were Exposed; Some Plaintext Passwords Also Leaked
Blockchain analytics firm Chainalysis disclosed in an updated security incident notice that the names, usernames, password hashes, and valid authentication tokens of all users had been exposed to the attacker, and that some customers’ plaintext passwords were also leaked through a separate attack method. After detecting abnormal activity, the company suspended KYT transaction monitoring, address screening, and login services, and required all users to reset their passwords and rotate API keys where necessary.
Previously, on October 30, Chainalysis first disclosed that it had been breached by a hacker using offensive AI agent technology; at that time it only confirmed that certain customer identity information had been accessed and said it had found no evidence that passwords or session tokens had been leaked.
11
Sui did this in May 2025: validators froze $162M taken from Cetus, then 90.9% voted for an upgrade that moved it to a recovery multisig.
On Polygon the freeze is already in place. The fork would move POL out of an address without its key. nitter.cf/WuBlockchain/status/21…
Polygon Labs Member Proposes Hard Fork to Recover Approximately 70.49 Million POL Stolen from Polymarket and Binance
A member of the Polygon Labs Validator Support Team has published a Polygon Improvement Proposal (PIP) suggesting a hard fork on the Polygon PoS mainnet to recover approximately 70.49 million POL stolen in two recent hacks involving Polymarket and Binance, valued at about $6.5 million based on October 29 prices. Of the total, Polymarket accounts for approximately 23.86 million POL, while Binance accounts for approximately 46.63 million POL. The related funds are currently restricted from transfer by block-producing nodes.
The proposal aims to move the POL balances from the attackers’ addresses to recovery addresses designated and verified by the two institutions through a hard fork, without changing the total token supply. The proposal will be submitted for discussion at the Polygon Protocol Governance Call on November 5. If approved, client development and testnet rehearsals are expected to be completed in approximately two weeks.
29
The Blast L2 has been shut down.
If you had any remaining ETH or USD in your L2 wallet, in a pending withdrawal, or in Blast Mobile, you can recover your assets at blast.io.
This recovery website will be active for 12 months, final support date Nov 4, 2027.
From @binance 's $6.34B report: pausing withdrawals didn't stop the drain. The attacker's contract already had partial control of a hot wallet through EIP-7702, and that permission lived on-chain.
So what you sign on-chain works until you revoke it on-chain.
3
1
43
In August BTCPay said only LND nodes were exposed and regular hot wallets were safe. Now hot wallets on 2.4.1 and earlier are being drained, Litecoin included.
If your BTCPay hot wallet predates 2.4.2, move it to a new seed now. nitter.cf/TheHackersNews/status/…
‼️ Hackers are exploiting a patched BTCPay Server flaw to steal Bitcoin and Litecoin from hot wallets.
Versions 2.4.1 and earlier were targeted. Users are urged to move to a fresh server and wallet, even if no theft is detected.
Here's what happened ↓ thehackernews.com/2026/11/ha…
60
azat retweeted
Imagine a stranger lends you $100M. No collateral, no name. One rule: pay it back in the same transaction.
In March 2023, Euler lost ~$197M to one. The loan wasn’t the problem. The missing check was. 📁
#flashloans #crypto
Thanks @altcoinbuzzio for citing our Solana tokenized stocks tracker in your piece on Backpack bringing META shares to Solana.
Per the tracker, Backpack is one of three issuers of META on Solana, alongside xStocks and Ondo.
altcoinbuzz.io/why-is-backpa…
1
1
80
In July someone tried to hack me on a work call.
I knew the guy. We’d met at a @EthereumDenver and I’d pitched him @trueholdxyz . Mid-call his Teams “broke” and he sent me a file, MSTeams SDK Update.scpt, saying it would fix it.
A .scpt file opens in Script Editor, which can run shell commands on a Mac. Microsoft has written up the same trick with a fake Zoom SDK update and tied it to Sapphire Sleet, a North Korean group that goes after people in crypto.
I didn’t run it. His account had most likely been taken over. So, If someone sends you an “update” in the middle of a call, end the call and message them somewhere else.
2
157
If you did run a file like this, treat that Mac as compromised:
- move funds out of any wallet whose keys or seed phrase were on it, from a different device
- log out of Telegram, your browsers and exchanges everywhere, and change passwords from a clean device
- check ~/Library/LaunchAgents and /Library/LaunchDaemons for anything you don't recognise
Then wipe it and reinstall macOS.
76















