
$XMR news
Every $XMR story, instantly, with how the price moved after each one.
Top stories
- Community Alert: An EU entity is suspected of losing $106M+ from multiple centralized exchange accounts yesterday (Nov 1). The suspected stolen funds were withdrawn as USDC & USDT by an illicit actor.Over the past 24 hours the illicit actor has been aggressively swapping USDC for ETH, transferring to instant exchanges (WellWallet, Kyrrex, etc), converting to XMR via Wagyu, and bridging across multiple chains.Theft addresses:0xADd95cD98E0288ba69785E3151E1db86adF8Dd580x29e9D7715D935e0D0D4B0DD0efC952A97E5510200x378B4f150707C283574DC89739608D29036D57d50x795a9d22F233024487161Fe6daFf73397c1626210x730Bcb1296758c377149d7409f98f041cf7239920x12D9012731eb0D54871A31Af5566Eb9ECCa351Db0x5A154f77852ed274Fd6F4c324a1Ee27809052FF70xA1096A66f9ed58A9594A6A1ad67A5472C09072240x90F0b6D51ed2FE2348A45b2C49BC441E959bc5570x8A97BC406180e28b11C5495fA099BF5119c6C6B00xd010cba790a6ab0048da18f2fbe8e3faf463a16a ZACHXBT
- 🚨 On-Chain Update: Tracking tools have flagged notable activity on wallet 0xb3fffca23d4444eE73349825ACD84f7b5020e387 👀 📊 Following a 10.39M USDC withdrawal from Lighter (@Lighter_xyz ) and an ETH swap via CoW Protocol, the address executed multiple 160 ETH transfers to wallets closely resembling its previous destinations—a pattern often associated with Address Poisoning attempts. ⚠️ Note: The nature of these transfers remains unconfirmed and may represent routine wallet management rather than a loss of funds. As always, verify full addresses carefully before transacting. 🔍 $LIT COINOTAG NEWS
- 🚨 UPDATE: Upbit and Bithumb pause $LIT deposits and withdrawals amid Lighter's security incident. Cointelegraph
- 🚨 Monero-bridged asset $XMR1 crashes and loses its peg. A market maker that stepped in to absorb the selling pressure reportedly suffered over $4 million in losses. Just four days earlier, funds linked to the Lighter incident had reportedly accumulated large amounts of $XMR1. #Monero #XMR1 #Crypto RATS
- ZachXBT says a suspected heist hit a victim in the EU for more than $106 million, and he's highly confident Lazarus Group wasn't behind it. Unchained
- International Law Enforcement Operation Targeting Opioid and Fentanyl Traffickers on the Dark Web Results in over 350 Arrests Worldwide and the Seizure of Drugs, Weapons, and over $234 Million USDOJ
- KRAKEN DROPS QUESTIONS ON HOW CLIENTS WILL USE WITHDRAWN MONERO Co-CEO @arjunsethi says affected clients need not respond. @krakenfx retains source-of-funds checks; $XMR stays listed with regional limits. Read more here: The Defiant
- ‼️ Monero swap site confirmed 3 months of its data leaked after a $5M extortion demand. Hudson Rock found 4,580 orders tying a public crypto deposit to a Monero address and the IP behind it. The leak still holds 4,002 orders flagged as deleted by users. International Cyber Digest
- Swapping on several blockchains has resumed following the 3.21.1 update. Trading blockchains: AVAX, BASE, BCH, BTC, DOGE, ETH, LTC, RUNE, TRON, XRPL, ZEC Halted blockchains: ATOM, BSC, SOL 14 active nodes still haven’t updated to 3.21.1. All active nodes need to update to 3.21.1 to fix performance issues with swapping. The 3.21.1 update also gets THORChain one step closer to launching Monero. THORChain
- Decibel keeps stacking markets on Aptos @DecibelTrade added six new perpetual futures markets today: WLD, ONDO, VVV, XMR, STRK and TIA. ONDO gets up to 10x leverage, VVV 3x, and the rest 5x. The exchange now lists more than 85 markets across perps and spot. Decibel has handled about $8.9B in total perp volume since its mainnet launch in February, including $1.2B in the last 30 days, per DefiLlama. It runs on @Aptos, which says every trade burns $APT through fees. BSCN
Latest
- Wrapped Monero token crashes 99.8% amid suspected $13.5M exploit COINTELEGRAPH
- Wrapped Monero Token Collapses 99% After $13 Million Hack Blamed on Web Host DECRYPT
- Wagyu's XMR1 wrapped Monero plunges 99% after $13 million hack as founder promises refunds THE BLOCK
- THE BLOCK: Wagyu's Wrapped Monero token $XMR1 plunged more than 99%, from around $500 to $0.65, following a $13 million hack. Pseudonymous founder PerpetualCow blamed a breach at Wagyu's hosting provider, saying the token's deployer key was exposed in files retained from a deleted server. Wagyu is temporarily unavailable, and the founder has promised personal refunds and a later relaunch. The Block
- 🚨 GoPlus Security Alert: Suspected #XMR1 Exploit on Hyperliquid—Deployer Address Transfers ~5.2M Tokens XMR1’s deployer address on Hyperliquid transferred approximately 5.2 million $XMR1 to a newly funded address. The recipient then sold the tokens into the order book, receiving approximately 13.3 million USDC. XMR1’s trading price plunged from around $494 to $1 in roughly 35 minutes. The proceeds have since been converted into approximately 7,300 ETH, most of which has been bridged to Ethereum: 0x1464dacaceb0d511f9964cdac5eba50ea42220bf XMR1 is a tokenized representation of Monero bridged to Hyperliquid via Wagyu. It is not native XMR on the Monero network. 🛡 Security Recommendations 1. Hold off on large XMR1 trades or cross-chain transfers until you have checked Wagyu’s official channels for updates on the incident and redemption status. 2. If you hold XMR1, monitor order book liquidity and bridge redemptions. Do not judge the asset’s value solely by its collapsed trading price. 3. Verify the asset and token identity before trading. Do not confuse XMR1 with native XMR, and watch out for fake announcements, compensation scams, and other phishing attempts exploiting the incident. GoPlus Security 🚦
- From Private Money to Programmable Privacy: Starknet’s Entire Financial Ecosystem Goes Private Zcash pioneered private money. Tornado Cash brought privacy to specific transactions. Starknet is taking the next step: programmable privacy across an entire financial ecosystem, without fragmenting liquidity or forcing users into new applications. For years, privacy has been one of crypto’s most important promises, yet one of its hardest features to use. Every swap, balance, transaction, and financial position recorded on a public blockchain can reveal information about its users. And while several projects have made significant progress toward solving this problem, privacy has often come with trade-offs: limited assets, isolated applications, fragmented liquidity, high costs, or complicated user experiences. What if privacy could simply become a feature of every financial application? That’s what Starknet is building. And with the rollout of STRK20 and Shadow Accounts across its ecosystem, much of that vision is already here. The evolution of privacy in crypto The history of onchain privacy can be understood through three major stages. 1. Private money: Zcash and Monero The first major breakthrough was making cryptocurrency transactions private. Projects like Zcash and Monero pioneered technologies that allow users to transfer and hold value without publicly exposing sensitive transaction information. They established an essential principle: financial privacy is possible on a public blockchain. But as crypto evolved beyond payments into lending, borrowing, trading, staking, and other financial applications, a new challenge emerged. Protecting transfers of a particular cryptocurrency was no longer enough. Users needed privacy across the entire financial system and for all assets. 2. Private transactions: Tornado Cash The next stage brought privacy tools to existing programmable blockchains. Tornado Cash demonstrated how users could use zero-knowledge proofs to break the publicly observable link between deposits and withdrawals on Ethereum. This was an important advancement: privacy no longer needed to exist exclusively within a dedicated privacy-focused blockchain. However, these solutions primarily addressed specific activities rather than providing an integrated privacy experience across DeFi. Users could make a transfer more private, but their subsequent interactions with lending markets, exchanges, liquidity pools, and other applications could still expose their activity. Privacy remained something users accessed separately from most of their financial interactions. Users also faced regulatory risks. For example, the U.S. sanctions imposed on Tornado Cash in August 2022 generally prohibited U.S. persons from transacting with the service. Even those who had deposited funds before the designation needed OFAC authorization to withdraw them. Although these sanctions were lifted in March 2025, the episode illustrated how regulatory action against a privacy tool could create barriers to accessing funds, including for users with legitimate privacy needs. 3. Programmable privacy: Starknet The next step is making privacy programmable. An entire financial ecosystem where users can choose to interact privately with the applications they already know. On Starknet, that means swapping, providing liquidity, trading options, staking, lending, borrowing, earning yield, and making payments with privacy capabilities integrated into existing applications. Importantly, this doesn’t require creating separate private versions of every protocol or splitting liquidity between public and private markets. Same applications. Same liquidity. Public or private modes. The design also addresses a key compliance challenge highlighted by Tornado Cash through deposit screening and strictly targeted disclosure. Regulatory disclosure is permitted only in response to a lawful request, and only for the specific users or transactions it covers. The wider privacy pool is never exposed: everyone else’s private activity remains confidential. This is what makes programmable privacy different. And STRK20 provides the infrastructure that makes it possible. STRK20: One privacy pool for an entire ecosystem STRK20 is Starknet’s privacy framework, enabling shielded balances, private transfers, and private DeFi for ERC-20 assets on Starknet. Its architecture addresses several limitations that have historically made onchain privacy difficult to adopt. One privacy pool, multiple assets; instead of requiring an isolated privacy pool for every token, STRK20 uses a shared, multi-asset privacy pool that supports every ERC-20 tokens on Starknet. Users can shield assets, hold private balances, and transfer them without publicly revealing the sender, receiver, or amount. Privacy without fragmented liquidity; STRK20 works with the DeFi infrastructure already deployed on Starknet. A private swap, for example, can execute against the same public liquidity used by regular traders. Low, predictable fees; privacy needs to be economically accessible if it is to become widely adopted. STRK20 uses a low, flat protocol fee for privacy actions of ~$0.12, rather than charging a percentage of the amount being protected. Privacy accessible from existing wallets; through supported wallets such as Bramble, Xverse, and Ready X, users can shield and unshield assets in just a few clicks, with near-instantaneous shielding flows. From there, they can access applications offering private modes. Privacy with targeted compliance; deposits are screened before entering the pool, and regulatory disclosure is restricted to the specific users or transactions covered by a lawful request. Everyone else’s private activity remains confidential. Shadow Accounts: Making DeFi programmable and private STRK20 introduced the foundation for private balances and transfers. Shadow Accounts extend that foundation to applications requiring persistent user identities, including staking, lending, liquidity provision, and trading. Each application can interact with a separate pseudonymous account whose connection to the user’s main wallet is not publicly exposed. This allows users to maintain positions and interact with protocols over time without directly linking those activities to their main wallet. Shadow Accounts don’t make every detail invisible: the pseudonymous account’s transactions and positions remain publicly observable. Their key privacy property is breaking the public link to the user’s primary identity. Together, STRK20 and Shadow Accounts enable privacy features to be integrated into existing DeFi applications. And the Starknet ecosystem has already put them to work. Introducing Starknet’s programmable privacy ecosystem In just a couple of months, privacy integrations have expanded across the entire Starknet ecosystem, bringing privacy capabilities to virtually every major category of onchain finance. Here’s what users can now do. Shield and unshield assets Bramble, Ready, and Xverse: Shield and unshield crypto assets directly from your wallet, providing an easy entry point into Starknet’s private financial ecosystem. Private trading and liquidity provision avnu; Private swaps: Swap assets privately while accessing existing public liquidity and routing infrastructure, without needing separate private liquidity pools. Ekubo; Private swaps and LPing: Swap tokens, provide liquidity, earn trading fees, and manage LP positions without publicly linking these activities to your wallet. SuperVega; Private options trading: Trade options and manage exposure through Shadow Accounts, bringing privacy to more advanced financial instruments. ArcX; Private points trading and yield generation: Trade points and access yield-generating strategies without publicly linking your activity to your main wallet. Private staking, lending, and yield Endur; Private staking and unstaking: Stake STRK and BTC, earn staking rewards, and unstake through privacy-enabled flows. Troves; Private yield generation: Access automated vaults and yield strategies, including strategies built on Ekubo, without publicly linking positions to you. Vesu; Private lending and borrowing: Lend and borrow assets through Shadow Accounts while maintaining access to Vesu’s existing lending markets. Opus; Private borrowing and stablecoin minting: Borrow and mint CASH, a Starknet-native stablecoin, without publicly linking the activity to your main wallet. Private everyday finance DashX; Private payroll: Enable businesses and organizations to pay contributors without publicly linking those payments to recipients’ identities. Haven; Private neobanking: Bring programmable privacy into everyday financial activities, including holding, transferring, and spending crypto through supported services. Taken together, these integrations represent something much bigger than a collection of privacy features. Users can now access a growing range of financial services with privacy built into the applications they already use, without fragmenting liquidity. They don’t need a separate blockchain for private money, another environment for private trading, and an isolated protocol for private yield. The infrastructure is shared, the applications are familiar, and liquidity can continue flowing through existing markets. This is the transition from isolated privacy solutions to programmable privacy across an entire ecosystem. For users, getting started is straightforward: Choose a supported wallet: Bramble, Ready, or Xverse. Shield your assets: Move tokens into the STRK20 privacy pool. Explore private DeFi: Swap, stake, trade, borrow, lend, and earn yield through the applications offering privacy-enabled flows. For developers, Starkzap has integrated STRK20 and Shadow Accounts, making it easier to add shielded balances, private transfers, and private DeFi to applications through a single TypeScript SDK, alongside its existing wallet and financial tools. Explore the Starknet Privacy Ecosystem → Build with STRK20 → For years, crypto has demonstrated that private money is possible. Now, Starknet is demonstrating that privacy can extend to an entire programmable financial ecosystem. Encrypt your life on Starknet. StarkWare
- #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 🚦
Loading the $XMR page…