
$ID news
Every $ID story, instantly, with how the price moved after each one.
Top stories
- Onchain data now confirms Binance hot wallets were drained. Here's what we know so far: → From about 20:10 UTC, Binance hot wallets on Ethereum, Arbitrum, Optimism, Base, Solana and Bitcoin, and likely Tron and Avalanche, sent funds to fresh attacker addresses. → Losses are $3.6B+, with public estimates up to ~$5.8B. → Every outflow was authorized with the hot wallets' own keys . How the attacker got signing access is not yet known. → On Ethereum, Binance 14 was taken over with EIP-7702 and is still delegated to the attacker's contract. → Tether and Circle have frozen part of the stolen USDT and USDC. ETH, SOL, BTC and most other tokens can't be frozen and some are already moving. Timeline (UTC) 1️⃣ 02:28: The attacker deploys a test version of a drainer contract. 2️⃣ 15:59: The drainer contract goes live. Only the attacker can call it. 3️⃣ ~20:10: Binance hot wallets begin sending funds to attacker addresses. 4️⃣ 20:20: One transaction carrying 50 pre-signed authorizations from Binance 14 delegates the wallet to the drainer contract. 5️⃣ 20:24: A single call sweeps ~167K ETH and ~64 tokens from Binance 14. 6️⃣ 20:41 and 20:59: The same delegation is used to move ~$823M USDC out of another Binance contract. 7️⃣ 21:04: Binance 14 is swept again. 8️⃣ Since then: USDT was swapped to ETH ahead of the freezes, and BTC is being split into 1,000 BTC chunks. What to do → Keep exposure to Binance reduced until Binance confirms its hot wallets are secure. → Do not send funds to Binance 14 (0x28c6c06298d514db089934071355e5743bf21d60). It is still delegated to the attacker's contract, so anything that arrives there can be swept. → Exchanges, OTC desks, bridges and other venues taking deposits: screen and block inbound funds from the attacker address (0x5227f603c1ee34ce3c06efe6477003bdfccb2f8c). Hypernative
- Securitize Reports Third Quarter 2026 Results PRN
- Coinone warns of phishing, identity theft after customer data breach COINTELEGRAPH
- NEWS: Ds review 181-page dossier from ex-Warren/Sanders staffers ID’ing hundreds of executives & corporations to target Envisions “resignations of major CEOs, hauling people in, material restitution” Tech giants, crypto, sports gambling, gas & more Jeff Stein
- 🚨 Hackers Breach at Least 27 Organizations Using Stolen Microsoft Entra ID and Azure DevOps Credentials An ongoing cyberattack campaign has compromised cloud environments belonging to at least 27 organizations, with attackers abusing stolen Microsoft Entra ID application credentials and Azure DevOps identities to gain access to Microsoft 365 and Azure resources. According to security researchers at Todyl, the campaign began on November 1, targeting managed service providers (MSPs) and their customers across government, energy, transportation, education, legal, and other sectors. Investigators have identified extensive unauthorized activity, including: • 27 organizations affected • 45 application registrations targeted • 33+ successful application authentications • Approximately 2,279 mailbox items accessed • 81 files downloaded from compromised environments • One application used to access 15 customer tenants Stolen information included password lists, private keys, VPN configurations, backup credentials, and remote access settings, raising concerns about additional compromises. Attackers were able to impersonate trusted applications and access cloud resources without triggering traditional user MFA challenges. No Microsoft vulnerability was exploited. Attack Details • Initial activity: November 1, 2026 • Targeted platforms: Microsoft Entra ID, Azure DevOps, Microsoft 365 • Attack method: Stolen application credentials and session token abuse • Confirmed source IP: 199[.]19[.]77[.]84 • Attribution: Unknown • Status: Ongoing investigation Organizations are advised to investigate unusual service principal activity, revoke compromised credentials, rotate exposed secrets, and review third-party application permissions. Dark Web Informer
- ‼️BREAKING: Ransomware gang The Gentlemen claims it hacked Nvidia, the AI chip giant. Its leak-site listing shows no stolen files yet. The data is marked "SOON", next to a countdown of about 10 days and a chat ID for ransom talks. The gang has a real track record. When its own internal data leaked in May, Check Point counted more than 1,570 victims, more than it had ever listed. Nvidia has not confirmed any breach. International Cyber Digest
- ALMOST A THIRD of iPhone Duo buyers RETURN it A 9to5Mac poll of nearly 6,000 early buyers found close to a third sent the foldable back, citing Touch ID, cameras, the tiny outer screen and even sand jamming the hinge RT
- OpenAI launches ChatGPT Wallet, allowing its 'dots' AI agents to make purchases for users CNBC
Latest
- Japan's Personal Information Protection Commission issued a notice urging rental car operators to promptly delete images of driver's licenses and other photo IDs after identity verification, following a data leak from unauthorized access. Noting no legal requirement exists to retain ID images post-rental despite keeping license numbers for two years. Public replies express frustration that the measure remains a non-mandatory caution without penalties, highlighting concerns over insufficient enforcement to prevent identity misuse. CZ 🔶 BNB
- Metis Rise FAQ The full rules are on this page. When a rule changes, we list the change and its start date under Updates on this page and email every applicant. The program What is Metis Rise? A monthly program for new AI agents deployed on Metis Andromeda Mainnet. It runs as a 3-month pilot. Builders who reach the qualifying thresholds compete for a monthly reward pool. How do I apply? Applications are rolling. Apply at When does my project enter the ranking? Applications submitted in one month enter the next month’s ranking. Projects that applied in October are ranked in November. Projects that apply in November are ranked in December, and so on. What do I need to qualify in a month? At least 15 unique valid users. A user counts when they make 3 or more qualifying transactions, or at least $2 in settled volume (m.USDC, m.USDT, or METIS) plus at least one legitimacy signal (a unique Telegram ID, Privy login, Web3 social handle, or a wallet older than 14 days / with prior Metis history). Please verify your contracts on the Metis Andromeda Explorer. It lets us count your users faster and more accurately. What is the reward? Up to $1,500 per month, shared by up to 3 qualifying builders ($800, $450, and $250), paid in METIS or stablecoins. If fewer than 3 builders qualify, fewer rewards are paid. The leaderboard What is the leaderboard? A block on the Rise page, updated daily, that shows the current Top 3 for the month. For each project, it shows the project name, estimated users, gas, and the time of the last update. It does not show wallet addresses. If no project has qualified yet, it shows: “No project has reached the 15-user floor yet this month.” Is the leaderboard the official result? No. It is a daily estimate built from public explorer data. The official result is the month-end snapshot, which runs the full checks (see “Month-end evaluation”). Why does the card say “Est. users” and not “Valid MAU”? Because the daily number is an estimate. A user is only confirmed as valid after the month-end checks. How are users counted each day? A daily job reads the public Metis explorer and applies the threshold: 3 transactions or $2 in settled volume per user. It leaves out: the project’s own wallets wallets funded by the project’s deployer self-transfers failed or test transactions The daily count does not check the legitimacy signal (Telegram ID, Privy login, social handle, wallet age). That check runs at month-end, so the month-end count can be lower. Why do some projects show “counting in progress”? Projects that take payments through a relayer need extra work to attribute transactions to the right end user. Until that is done, the board shows “counting in progress” instead of a number that could be wrong. This is a data issue, not a penalty. My users pay through a relayer. How are they counted? We count the user who signed the payment, not the relayer, when the contract records the signer. If it does not, we may ask you for a list of payments that we can check on-chain. A relayer you run counts as one of your project’s wallets, so user wallets it funds do not count. Does the leaderboard show who will win? No. A project’s position on the daily board does not guarantee a reward. Rewards depend on the month-end evaluation. How ranking works How is the ranking calculated? The rules weight users at 80% and gas at 20%. The formula that combines them is: score = 0.8 x (users / highest users) + 0.2 x (gas / highest gas) “Highest” means the highest among projects that have reached the 15-user floor. A project scores only once it reaches the floor. For the $2 volume test, m.USDC and m.USDT count at $1 and METIS at the explorer’s METIS price when the daily job runs. Does gas from my own wallets count? No. Gas is counted only from counted users’ transactions, so excluded wallets add nothing to either users or gas. Can a project win without reaching 15 users? No. The 15-user floor applies to every project. Month-end evaluation What happens at the end of the month? The same daily job produces the month-end numbers. The full funding-source checks are run on the snapshot, as published. Reviewers then examine the evidence for the Top 3. Who reviews the Top 3? Reviewers from the Metis team check the evidence for every Top-3 project. Reviewers are not linked to any applicant. Why aren’t winners announced on the last day of the month? Because projects get 7 days to respond to any finding before results are final. Where are results published? Monthly results are posted under Updates on this page in the first week of the next month, with the reward amounts. What counts as a finding? Anything in the evidence that may disqualify a user or wallet, for example a wallet funded by the project or reused across projects. The project is told what was found and can answer within 7 days. Fairness rules Are linked projects allowed? Yes. A link between projects does not disqualify anyone. User wallets funded by the project do not count (for wallets a project’s bot holds, see the next answer); a user wallet counts for one entry only, and an inaccurate answer to the wallet declaration can disqualify a project after it has seen the evidence and had 7 days to respond. Do wallets that my bot creates for users count? In November 2026, yes, if each wallet belongs to a real, separate person and was not funded by your deployer, your relayer, or a shared source. From 1 December 2026, only wallets the user controls count: self-custodial wallets (MetaMask, Rabby, WalletConnect) or user-owned embedded or passkey wallets (Privy, GOAT AgentKit). Wallets whose private keys are created and stored on your project’s server no longer count. This applies to every project, including those already in the program. What is the wallet declaration? Every team is asked to declare its wallets and any relationship to other entries. The same question is sent to every team. Can one builder win more than one slot? One builder or connected team can take one reward slot per month: the slot of its highest-ranked project. Several projects may still enter and appear on the board. Do I have to post about Metis on X? We encourage it. A launch thread on X helps us feature your project. Please include: Your live product on Metis Andromeda, and what the agent does One concrete example of it working (a task, a report, a payout) A link to the product or contract address A tag for @MetisL2 and the hashtag #MetisRise Keep it specific. A real example of the agent doing its job will do more than a general description. Metis🌿
- - ALL VALIDATOR OPERATORS: 🚀 The next Sui v1.84.1 upgrade for mainnet is now available. This release includes protocol version 142, which will activate at the next epoch boundary once 83.4% of validators by stake have upgraded. Please also update your bridge. Thank you! Branch: mainnet Commit: e83d69069e4023cce4a2dcde2b9c74384418fee1 Tag: mainnet-v1.84.1 Release Notes: Release mainnet-v1.84.1 · MystenLabs/sui Protocol Sui Protocol Version in this release: 142 #28590: Protocol version 141 counts accumulator writes, ID-only object changes and unchanged consensus objects toward the transaction effects size... Sui
- What would you build with Agent ID? @BNBCHAIN and Binance Wallet are launching the Agent ID Hackathon. Create and compete for a 60,000 USDC prize pool and a unique two-character Agent ID. Bring your build: Binance Wallet
- Agent ID Hackathon: Build Decentralized Applications (dApps) Around Agent ID to Win 60,000 USDC Worth of Rewards Binance EN
- After Tencent Cloud, Bittensor subnet @chutes_ai has partnered with @alibaba_cloud. GLM-5.3 and DeepSeek V4.1 Flash are 35% off on Chutes through November 23. Openτensor Foundaτion
- #Lighter Incident Breakdown: Nonce Reuse in Custom Signing Code Enabled API Private Key Recovery 1️⃣ Affected Accounts An attacker derived the API private keys for two trading accounts on Lighter and used them to move funds out of those accounts. Approximately $15.48M was reportedly affected, with around $5M in USDC recovered and returned to the affected trader by the Lighter Security Council. Reported affected accounts: Account 1: Lighter Account ID: 714710 Associated onchain address: 0x0d1D09312665D31Ed68231b88079a245E0458F6F Amount affected: ~$10.39M Account 2: Lighter Account ID: 714723 Associated onchain address: 0x66Cf2f85115CC20bF439720927C1f93De9672068 Amount affected: ~$5.09M 2️⃣ Root Cause The affected accounts used insecure, unofficial signing code that reused cryptographic signing nonces across different transactions. This allowed the attacker to derive the API private keys from publicly available signatures. Lighter said its protocol, smart contracts, and official SDKs were unaffected. The attacker moved the funds through the following sequence: Create a public pool using the compromised account → Mint pool shares to an attacker-controlled account → Transfer the victim’s funds into the pool, increasing its net asset value (NAV) without issuing corresponding shares to the victim → Redeem the attacker’s shares and withdraw the funds. 3️⃣ Funds Withdrawn The attacker withdrew approximately 10.39M USDC from Lighter and swapped the proceeds for ETH. Onchain tracing identified part of the proceeds moving through multiple wallets to buy XMR1 on Hyperliquid. XMR1 should not be conflated with native Monero ($XMR). The available evidence does not establish that these purchases drove up Monero’s price. 4️⃣ Reported Attacker Account and Address Lighter Account ID: 769455 Associated onchain address: 0xb3fffca23d4444eE73349825ACD84f7b5020e387 🛡️ Security Recommendations ▪️ Use Lighter’s official Python, Go, or TypeScript SDKs, or its Agent Kit. Avoid implementing your own signing logic. ▪️ Let the official signer handle cryptographic signing nonces. Never reuse a signing nonce or substitute timestamps, counters, weak random values, or cached values. Signing nonces are distinct from transaction nonces. ▪️ If your code may have reused signing nonces, revoke and replace all related API keys immediately. Fixing the code alone isn’t enough. ▪️ Enable IP allowlisting and per-key permissions and limits as they become available. Separate permissions for trading, transfers, pool creation, and redemptions wherever supported. ▪️ Lighter now requires wallet signatures for transfers into public pools and no longer exposes API signatures publicly. GoPlus Security 🚦
- Agent ID claims have surpassed 200,000! 🎉 Unique name. Non-transferable. The on-chain identity for Agents is being adopted faster than ever. The ecosystem is thriving. More to come soon. Binance Wallet
- a few things you might’ve missed while the devs were busy this week. 1 / KOB @crono_walker launched a testnet order book built with SilverScript and Argent. lets people place buy and sell orders for tokens, with Kaspa L1 contracts enforcing the trading rules. open to try on testnet-10. 2 / home nodes @OriNewman proposed a Rusty Kaspa update to help nodes behind home routers connect to each other without manually setting up port forwarding. still under review. 3 / prediction markets @manyfest_ shared work with @maxibitcat on a permissionless prediction market built with Argent. predictions would be tradable tokens, with a voting system to settle outcomes. still in development. 4 / HardKAS @HardKASOfficial is building a practice environment for Kaspa app developers. it lets them send test payments and try out smart contracts on their own computer, using coins with no real value. the idea is to find bugs before real money is involved. still experimental. 5 / notes for coding agents @KasperoLabs published a free guide for AI agents building on Kaspa. covers wallets, payments, SilverScript and mistakes found while building real projects. Kaspa
- The Machinery Is Open: Intuition Packages and Core v2 From day one, Intuition has been built around open data. Anyone can make claims about anything, and anyone can explore what others have shared. But making data open is only part of the picture. The tools used to work with that data, the rules for organizing it, and the infrastructure that makes it accessible are just as important. Until now, those parts haven’t been as open to the people building on Intuition. Today, that changes! We’ve released 21 open-source TypeScript packages under @0xintuition on npm as an alpha version for developers to explore and build with. Intuition Core v2, the backend that developers can host themselves to power the Intuition knowledge graph, is already running on these packages. Intuition’s data has always been open for anyone to use. Now, the technology behind it is open-source too, making it easier than ever for developers to start building. Setting the Standard Every knowledge system eventually faces the same problem: people can refer to the exact same thing in different ways. Take Radiohead, for example. Someone writes “Radiohead,” another writes “RADIOHEAD,” and someone else writes “Radiohead “ with an extra space at the end. To us, these are obviously the same band. But machines don’t automatically recognize them as the same thing. As more people contribute information, these small differences can create duplicate entries, making it harder to connect information about the same thing. The traditional solution is to have a central authority that assigns unique identifiers to everything, making sure everyone refers to the same thing in the same way. But this creates another problem: everyone depends on that central authority to assign identifiers. That’s exactly the kind of dependency an open knowledge graph is designed to avoid. To solve this, we need a reliable way for different people and applications to identify the same things, in a decentralized manner. Intuition IDs: A Shared Language for Everything Intuition IDs solve this problem differently. Instead of relying on a central authority to assign identifiers, Intuition uses a shared set of publicly available rules to generate consistent IDs from existing information. Take books, for example. Many published book editions already have a unique identifier called an ISBN. Intuition can use that ISBN to generate its own ID. For example, the ISBN 9780684832722 becomes int:isbn:9780684832722. Anyone following the same rules will arrive at the same result. Whether someone adds the book from London, New York, or through an AI agent running at 3 AM, the ID will be identical. This allows people and developers to independently contribute information about the same things and connect their contributions to the same entries in the Intuition knowledge graph, rather than creating unnecessary duplicates. Today, we’re releasing the technical specification, tests to verify that implementations follow the rules correctly, and a working reference implementation developers can use. These cover 29 different identifier schemes, including ISBNs for books, ISRCs for music recordings, Wikidata entries, and Ethereum accounts. Introducing Intuition Packages Information is only useful when we can understand what it describes. That’s why we’ve made it easier for developers to turn simple links or text into structured, detailed entries (called atoms) in the Intuition knowledge graph. These new packages help developers do three things: Parsing: Automatically identify links from 21 platforms, including GitHub, Spotify, Wikipedia, YouTube, and IMDb. Enrichment: Retrieve additional details through 40 provider adapters, many of which work without requiring API keys. Shared vocabulary: Use 37 predefined entity classifications, pre-made creation profiles, and a registry of 133 predicates (ways to describe relationships), so developers can organize and connect information using the same standards. With these tools, developers can turn a simple link into a structured, information-rich atom in just a few lines of code. For Agents and Apps The next wave of contributors to the world’s knowledge won’t all be human. AI agents will also play a role, and we’ve designed our tools with that future in mind. The new SDK 4.0 alpha gives developers building with Node.js, browsers, and AI agents the tools to read information from Intuition, prepare onchain actions, and generate consistent IDs. This means developers can know an atom’s ID before it’s even written onchain. Alongside it, we’ve released the new intuition CLI, a command line tool that allows AI agents to prepare blockchain transactions and action plans without needing access to a wallet. This means AI agents can explore information, plan actions, and prepare transactions without actually executing them. The final signing and authorization remain separate, giving developers control over what gets executed. Run It Locally For a system to be truly open, developers shouldn’t have to depend on someone else’s servers to use it. That’s why Intuition Core allows anyone to run their own backend for the Intuition knowledge graph. It includes the tools needed to process blockchain data, organize information into atoms, and make that information accessible to applications. Developers can get started with a single command, without needing any paid accounts. Intuition Core v2 runs on the same open-source packages available to everyone. It also introduces optional support for Intuition IDs, allows the same entity to be found through multiple identifiers, and improves security by keeping provider API keys out of responses and stored diagnostic information. Get Involved Everything we’ve released is open-source under the MIT license, meaning anyone can freely use, modify, and build on it. This is still an early release for developers, and we’re looking forward to improving it together with the community. We quite literally cannot build a crowdsourced knowledge graph alone. That’s why we want to hear from builders: what works, what breaks, what’s missing, and most importantly, what you’d like to build with it. Ready to explore? Start here... Intuition Packages: Intuition Core v2: And, join our Discord community to connect with other builders, share feedback, ask questions, and get involved! TRUST the process 👁️ Intuition 👁️
- [Security] octez.connect v5.0.5: pairing and session-control fix 🔒 *Joint post by Nomadic Labs, TriliTech and Functori* octez.connect v5.0.5 fixes vulnerabilities in pairing and session-control validation inherited from the Beacon SDK. These issues do not expose wallet private keys and do not allow anyone to forge signatures from a user's wallet. ⚠️ Action required • dApps on @tezos-x/octez.connect-* ≤ 5.0.4 (incl. 4.8.x): upgrade to 5.0.5 • dApps on @tezos-x/octez.js-dapp-wallet 25.0.0 or 25.1.0-rc.0: upgrade to 25.0.1 or 25.1.0-rc.1 (octez.js release in progress) • Taquito with the ECAD packages: upgrade to @taquito/*@25.1.1 • Wallets built on the octez.connect wallet SDK: upgrade to 5.0.5 • Suspect your dApp was targeted? Clear stored peers and ask users to re-pair ℹ️ Behavior change Reloading the page while a pairing is in progress invalidates it: users will need a fresh QR code or deep link. Completed pairings restore normally. 🔧 What was fixed • Pairing responses must match a live, single-use pairing request, with its ID • Matrix room invites and routing are only trusted once the sender is authenticated • senderId is bound to the sender's key, ChangeAccountRequest is only accepted from the active peer, and Disconnect from an unknown wallet is ignored • Closing the pairing popup invalidates its QR code 🙏 Thanks To David Kaminski (@dvkam) for discovering and reporting these issues, and to ECAD Labs for the hardening, testing and coordinated disclosure, and for the fixed @ecadlabs/beacon-* and Taquito releases. 📖 Full announcement: < 💻 GitHub: < 📦 npm (octez.connect): < 📦 npm (octez.js): < Tezos
Loading the $ID page…