Bitty Vault

Here’s the follow-up we promised on our investigation into the reported implant in a Trezor Safe 5 bought from CryptoBilis. Our findings, and what we’ve changed since, are in the article below:

What this means for Keplr users If you created your Keplr wallet with a recovery phrase or a hardware wallet, you are NOT affected. In response to Web3Auth’s infrastructure vulnerability leading to private key breach some Keplr users who signed in with Google or Apple, we are assisting the Web3Auth team’s effort to secure and protect assets from affected users. This is ongoing. Staked and locked assets add complexity and take longer. This means some Google/Apple-login accounts may already show a reduced or empty balance as a result of these mitigation efforts. If you created your Keplr account with Google or Apple login, your account may be affected:
– Do not send new funds to that account.
– Move any remaining liquid assets to a recovery-phrase or hardware-wallet account. We are working with Web3Auth on a way to check whether your account is affected.  Only trust updates from this account or @Web3Auth. Ignore DMs or links offering “recovery”.

INTEL: $4.06M DRAINED FROM IPHONES WITH ONE SAFARI CLICK DarkSword is an iOS exploit kit Google, Lookout and iVerify tracked in the wild. On iOS 18.4–18.7, opening a malicious site in Safari is enough. No wallet connect. No signature. No approval. What it steals from the phone: > Keychain credentials > Notes and Photos (seed screenshots) > Crypto wallet files and private keys Bitquery then followed the money on-chain (5 Oct – 4 Nov UTC): > At least $4.06M USDT from 365 TRON wallets > 43 collector wallets tied to one fee wallet >+$103K from 65 wallets on 8 other chains > One theft matches a published iPhone victim to the second SlowMist also mapped 1,500+ related phishing domains. This is not a Trust Wallet bug - it's the phone. Do this now: 1. Update iOS (18.7.7+ or iOS 26.3+) 2. Never store seeds in Photos, screenshots or Notes 3. If an unknown wallet just sent you a few TRX/ETH for "fees," move funds to a fresh wallet on a clean device

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…