News
30 Apr 2026, 01:35
Satya Nadella OpenAI Deal: Microsoft CEO Exploits New AI Partnership for Massive Revenue Growth

BitcoinWorld Satya Nadella OpenAI Deal: Microsoft CEO Exploits New AI Partnership for Massive Revenue Growth Microsoft CEO Satya Nadella has made it clear: the company intends to fully capitalize on its revised partnership with OpenAI. During a recent earnings call, Nadella addressed questions about the new deal’s financial impact. He emphasized that Microsoft now has royalty-free access to OpenAI’s most advanced AI models through 2032. “We fully plan to exploit it,” he stated. This statement comes as Microsoft reports its AI business has surpassed an annual revenue run rate of $37 billion. Understanding the New Satya Nadella OpenAI Deal The revised agreement marks a significant shift in the relationship between Microsoft and OpenAI. Previously, Microsoft held exclusive access to OpenAI’s technology. Now, that exclusivity is gone. OpenAI has announced partnerships with other cloud providers, including Amazon Web Services. Despite this, Nadella remains confident. He highlighted that Microsoft retains all IP rights to OpenAI’s frontier models. This includes access to their latest AI agents and products. Key Financial Terms of the Partnership The deal includes several critical financial components. Microsoft no longer pays licensing fees for OpenAI’s models. Instead, the company benefits in other ways. OpenAI has committed to purchasing over $250 billion worth of Microsoft cloud services. Additionally, Microsoft holds a 27% equity stake in OpenAI. This structure ensures a “win-win” for both organizations, according to Nadella. Deal Component Details AI Model Access Royalty-free through 2032 Cloud Commitment OpenAI to spend $250B+ on Azure Equity Stake Microsoft owns 27% of OpenAI Exclusivity No longer exclusive; OpenAI works with rivals How Microsoft Plans to Exploit Its AI Access Nadella’s use of the word “exploit” was deliberate. He explained that Microsoft will integrate OpenAI’s technology across its entire product suite. This includes Azure, Microsoft 365, and Dynamics. The company has already seen massive growth. Its AI business revenue run rate hit $37 billion, a 123% year-over-year increase. This growth demonstrates the immediate value of the partnership. Enterprise Customers and Multi-Model Strategy Nadella also addressed concerns about OpenAI’s relative importance. He noted that enterprises increasingly use multiple AI models. Microsoft offers the broadest selection of any hyperscaler. Customers can choose from OpenAI, Anthropic, and open-source models. Over 10,000 customers have used more than one model. This strategy reduces dependency on any single AI provider. Market Reaction and Industry Impact Wall Street analysts had speculated the new deal might weaken Microsoft’s AI edge. The loss of exclusivity raised concerns. However, Nadella’s comments and the strong earnings report have reassured investors. The company’s cloud growth remains robust. Profits continue to rise. The deal appears to be a strategic win for both parties. Comparison with Competitors OpenAI’s new partnership with Amazon marks a major industry shift. Sam Altman and AWS CEO Mark Garman have publicly discussed their collaboration. This move signals that OpenAI wants to diversify its cloud infrastructure. Microsoft, meanwhile, retains its privileged access to OpenAI’s best models. The competitive landscape is evolving rapidly. Microsoft : Retains IP rights and cloud revenue from OpenAI OpenAI : Gains multiple cloud partners and financial flexibility Amazon : Secures exclusive AI products from OpenAI Enterprises : Benefit from broader model choice and competition Timeline of the Microsoft-OpenAI Partnership The relationship began with a $1 billion investment in 2019. Microsoft later invested billions more. The partnership deepened with each funding round. In 2023, OpenAI’s rapid growth led to governance changes. The revised deal announced in 2025 restructures financial terms. It also ends Microsoft’s exclusive access. This timeline shows a strategic evolution from investor to key customer. Expert Analysis on the Deal’s Long-Term Impact Industry experts view the deal as a hedge for both companies. Microsoft secures access to cutting-edge AI without ongoing costs. OpenAI gains financial stability and multiple cloud partners. The $250 billion cloud commitment ensures long-term revenue for Microsoft. The equity stake provides upside if OpenAI’s valuation grows. This structure aligns incentives for the next decade. Conclusion The Satya Nadella OpenAI deal represents a strategic masterstroke. Microsoft retains access to frontier AI models through 2032. It no longer pays licensing fees. Instead, it benefits from a massive cloud contract and equity stake. The company’s AI revenue has already reached $37 billion annually. Nadella’s confidence in exploiting this partnership is well-founded. Time will tell if this win-win deal holds, but Microsoft’s current trajectory is strong. FAQs Q1: What is the Satya Nadella OpenAI deal? The deal restructures Microsoft’s partnership with OpenAI. Microsoft gets royalty-free access to OpenAI’s AI models through 2032, while OpenAI commits to spending $250 billion on Microsoft cloud services. Q2: Why did Nadella say he will ‘exploit’ the deal? Nadella used the term to emphasize Microsoft’s intent to fully leverage OpenAI’s technology for its products and services, including Azure, Microsoft 365, and enterprise solutions. Q3: Does Microsoft still have exclusive access to OpenAI’s tech? No. The new deal ends Microsoft’s exclusivity. OpenAI now works with other cloud providers like Amazon Web Services. Q4: How much is Microsoft’s AI business worth? Microsoft reported an annual revenue run rate of $37 billion for its AI business, a 123% increase year-over-year. Q5: What is Microsoft’s stake in OpenAI? Microsoft holds a 27% equity stake in OpenAI. It also has a $250 billion cloud services commitment from the company. This post Satya Nadella OpenAI Deal: Microsoft CEO Exploits New AI Partnership for Massive Revenue Growth first appeared on BitcoinWorld .
29 Apr 2026, 17:56
AAVE rsETH Crisis: DeFi Bent, Not Broken

DeFi was shaken by the KelpDAO rsETH exploit but, according to Standard Chartered, it didn't break. 292M rsETH was funneled into Aave, resulting in a 17B dollar deposit loss. The coalition committe...
29 Apr 2026, 17:38
13.71 Billion SWEAT Tokens Drained In Seconds From Multiple Foundation Wallets In An Exploit Of Mass Penetration

The Sweat Economy ecosystem is facing a critical security breach after roughly 13.71 billion SWEAT tokens were suddenly withdrawn from multiple wallets controlled by the Sweat Foundation in seconds. The incident occurred suddenly on April 29, 2026 and represents one of the largest token extraction events in recent decentralized finance (DeFi) history. SWEAT Token Drop About 50% In A Month – Source: CoinMarketCap On-chain data shows that the attack occurred over a 30-second window starting at 13:36 UTC. In this time window, numerous wallets associated with the foundation were fully emptied to zero balances. What we observe in terms of speed and cooperation indicates a high level of planning and technical professionalism.The scale of the breach is especially worrying since the tokens were about 65% of total circulating SWEAT supply. The swift transfer of even this broad range of tokens from wallets it controls has raised alarm over the integrity of the Sweat Economy ecosystem & market stability. Community Alert: Ongoing exploit on @SweatEconomy on @NEARProtocol . Exploiter: 3be304b2151870b2be88b9de0b80acab921337ad152584138bd852fc6e9ae018 Largest exploit tx: DvrSMfY85Anc6AuLUmoEDkDdab7qX5NUZLu76HN8NoPn — Blockaid (@blockaid_) April 29, 2026 Customized Drainer Contract And Instant Transactions Attack Further analysis shows the attacker had employed a custom drainer contract designed specifically for this execution of the attack. According to reports, this contract associated with an “exploit-resolve” module built in Rust enabled rapid token extraction and transfer over multiple wallets. This attack was almost instantaneous, dissimilar from most exploits that happen over long periods of time. The fact that several wallets were drained at the same time, reflects a high degree of automation and evidence of pre-attack preparedness, which are quite different from opportunistic attacks. At the time of writing, blockchain records indicate that the attacker regained control over nearly 17.71 billion of the SWEAT tokens worth about 3.46 million US Dollars ($3.46 million). These figures also include assets traveling through the different stages of the exploit’s transaction pipeline. An in-depth analysis unpacks roughly $2.68 million kept within a mainset aggregation wallet, around $761,000 channeled through an intermediary staging address, and the residual, around $20m, previously exchanged into alternative assets like NEAR and USDC. Multiple Sweat Foundation accounts were drained to zero in a single ~30-second window starting 2026-04-29 13:36 UTC. Total extracted: ~13.71B SWEAT (~65% of supply). Funds are being routed via Ref Finance and Wormhole/Portal Bridge. The exploiter address is running a custom… — Blockaid (@blockaid_) April 29, 2026 Funds Funneled Through Ref Finance And Cross Chain Bridges The attacker then passed the stolen tokens through a number of DeFi channels, apparently to hide the source of original funds and make it more difficult to track. In particular, transactions went through Ref Finance, the largest DeFi based on the NEAR Protocol network. In addition to on-chain swaps, the attacker also used cross-chain bridges (such as the Wormhole / Portal Bridge) to move funds between heterogeneous blockchain ecosystems. Deploying this tactic disperses assets to various ledgers and jurisdictions, making it more difficult for forensic activities. Bridging protocols create tremendous complexity for investigators, since transfers across chains present both technical and legal hurdles. Fragmentation of asset trails hampers coordinated recovery and enforcement actions. However, all blocks and transactions are stored entirely in public databases known as block explorers, which allow one to follow wallets real time since blockchain is inherently transparent. Security firms and on-chain intelligence platforms are still tracking fund movements as the situation unfolds. Security Concerns As Community Is Waiting For The Reply The exploit has caused a stir in the DeFi community, mainly because of the size of the breach and because it specifically attacked wallets controlled by benevolent deeds performing entities. Notably, no official statements regarding the effect on user funds included in the data available as of press time, but the seriousness of the attack raises urgent concerns about whether sufficient security safeguards exist within the protocol. As investigations continue, community alerts have warned users to beware of contracts or marketplaces linked with the investigation. This incident points to the importance of continuous surveillance for anomalous activity on the network with a short notification time of investigator engagement and prompt incident response that is consistent in decentralized ecosystems. The immediate focus on Sweat Economy is containment, forensic investigation and regaining the confidence of its users and stakeholders. The mere loss of 99%+ of the supply in and out, is not something that tokenomics or a dynamic ecosystem can navigate well as it also dramatically increases the volatility risk profile over the long term. On a larger level, this incident highlights the ongoing weaknesses in DeFi infrastructures. As these platforms grow in size and complexity, both the incentives for attack and the means by which they can be successful also increase, making security a necessary shift from being considered a feature to being treated as an essential basis of existence within the blockchain environment. Disclosure: This is not trading or investment advice. Always do your research before buying any cryptocurrency or investing in any services. Follow us on Twitter @nulltxnews to stay updated with the latest Crypto, NFT, AI, Cybersecurity, Distributed Computing, and Metaverse news !
29 Apr 2026, 16:45
DeFi faces rising losses as AI-driven attacks escalate

The series of attacks on the Ethereum mainnet that led to over $1.5 million in losses has been exacerbated by new research that shows that artificial intelligence (AI) agents can now autonomously discover and exploit vulnerabilities in decentralized finance protocols. Security firm GoPlus Security reported that four separate contracts were exploited in just 48 hours ending April 29. The firm warned that hackers armed with AI are becoming more precise and faster than ever. And DeFi smart contract developers have nowhere to turn to except AI to tackle the problems that AI itself started. Can AI really hack DeFi by itself? a16z crypto tested an off-the-shelf AI coding agent against 20 past price manipulation incidents on Ethereum and found that when given just a contract address and basic tools, the AI succeeded in exploiting the vulnerability only 10% of the time. However, when researchers gave the agent access to structured knowledge about common attack patterns like vault donation exploits and automated market maker (AMM) pool manipulation, the success rate jumped to 70%. The researchers noted that while the AI is very good at finding bugs, it sometimes struggles with complex, multi-step attacks. One agent even tried to “escape” its test environment by extracting a secret key to look at future block data. Anthropic recently announced a new AI model called “Claude Mythos Preview.” The company stated that this model can autonomously find and write working exploits for zero-day vulnerabilities across major operating systems and web browsers. Before Mythos Preview , older models had a “near-0% success rate” at writing exploits. The company also confirmed that the same improvements that make the model good at patching vulnerabilities also make it good at exploiting them. When given access to Etherscan’s transaction API, the agent found actual past attack transactions and reverse-engineered them to write its own exploit code. How much was lost in the ZetaChain hack? GoPlus Security flagged four separate smart contract exploits on Ethereum mainnet within a 48-hour window ending April 29. The combined losses exceeded $1.5 million. The firm has described the current pace of AI-assisted attacks as a “countdown-by-the-second era.” In one of the week’s larger incidents, approximately $333,868 was drained across nine transactions on four chains, including Ethereum, Arbitrum, Base, and BSC. ZetaChain’s official post-mortem report says that no user funds were lost; the three affected wallets belonged to the ZetaChain team. The attacker took advantage of a feature in the GatewayEVM contract using “arbitrary calls.” The gateway lacked a strict blocklist, allowing the hacker to instruct it to transfer token allowances that had been set by the team wallets. The hacker funded wallets through Tornado Cash three days before the attack while mimicking a victim’s wallet. ZetaChain admitted that the vulnerability had been reported earlier through its bug bounty program, but the initial reports were dismissed. The protocol has since paused cross-chain transactions and is rolling out a patch to disable the risky code. Other Ethereum exploits identified by GoPlus Security over the past 48 hours include an onchain aggregator contract that lost roughly $983,000 due to missing access controls; an unauthorized third-party vault tied to TradingProtocol that lost roughly $398,000 also due to missing permission checks; a BCB contract that lost roughly $39,800 from a reentrancy vulnerability; and a QNT asset contract that lost roughly $124,900 from an arbitrary call vulnerability. Cryptopolitan reports that DeFi losses in April alone have reached record levels, surpassing the combined stats for the first three months of the year. With mounting losses in recent cases, it is setting up an epic showdown where hackers and developers are fighting AI with AI. With Anthropic’s Mythos and others now entering the conversation, it is looking like AI is arming hackers and developers won’t have any choice but to use AI to defend themselves Don’t just read crypto news. Understand it. Subscribe to our newsletter. It's free .
29 Apr 2026, 16:15
Aave scrambles to revive lending in wake of KelpDAO exploit

Aave struggles to bring back borrowers and lenders since the Kelp DAO hack. The DeFi protocol started a campaign to rebuild the rsETH collateral, but other vaults also stay inactive. New loans on Aave have ground to a halt, with only an outlier of $32M borrowed as of April 28. Activity has fallen to almost negligible levels as the protocol and DeFi as a whole try to rebuild trust. Aave lending activity ground to a halt, despite higher than usual rates for lenders. Almost no new loan events were recorded following the recent KelpDAO hack. | Source: CryptoQuant . Aave total value locked slid to around $14B, down from over $25B before the hack. Fees remained at their baseline of $2.8M daily. As Cryptopolitan reported, on the busiest days after the hack, Aave saw outflows of over $15B . Aave lending rates remain elevated Aave lending rates remain elevated, with up to 6.38% for USDC borrowing. During the latest freeze of rsETH, the protocol offered over 13% in lending rates, but could not overcome investor fears. USDC vaults remained at 100% utilization, discouraging other lenders to risk their funds in the aftermath of the KelpDAO hack. As a result, Aave now offers better rates than the DeFi baseline, but lenders and borrowers are still reluctant to return. The latest Aave V3 data show stablecoins and WETH saw the most significant breakdown of lending, with outflows of leverage. Borrowing was still active for liquid assets like USDT, USDC, and WETH, but loan events slowed down to almost zero, based on CryptoQuant data. Based on Dune Analytics data, WETH is the most widely borrowed asset, with $6.5B in loans. $3.7B were borrowed in USDT, and $2.9B in USDC. The recent higher lending rates suggest Aave did not see increased demand for capital, but a liquidity stress event. Borrow rates spiked, increasing their APY to over 14%. Later, rates corrected, but remained elevated at 7.12%. Lenders have become more defensive, leading to more expensive capital for DeFi. Is another DeFi winter coming? The recent lending crunch shows DeFi went through one of its most significant borrowing collapses. This time, Aave survived, but raised questions of the resilience of DeFi. The previous DeFi winter followed the crash of FTX and Terra (LUNA), causing a two-year slump in DeFi activity. Some whales moved their funds immediately, shifting to Spark Protocol as one of the more secure DeFi locations. Aave’s founder Stani Kulechov still expressed confidence in the protocol, despite the lending crunch. He remarked that Aave had survived multiple bear cycles, and would be capable of a ttracting liquidity again. “ For me personally, the rsETH bridge incident was unfortunate as our team and community has put so much effort into securing the protocol and seeing the exploit happening outside of the protocol smart contracts, and affecting the markets is hard to watch even when the markets had (and still have) full backing like Mainnet Core,” remarked Kulechov in a recent X post . In the past few days, crypto influencers expressed their support for Aave and showed a readiness to return to lending and yield generation. The Aave protocol is also voting on a freeze of buybacks, until DeFi conditions improve. The vote will most probably resolve to ‘yes’ in two more days. The slower lending still pressures the AAVE token, which slid to $93.21 in the past week. If you're reading this, you’re already ahead. Stay there with our newsletter .
29 Apr 2026, 15:31
Litecoin MWEB exploit resolved, block reorganization corrected

Litecoin recently faced one of its most serious technical incidents tied to the Mimblewimble Extension Blocks (MWEB) feature, after a validation flaw allowed an attacker to generate an inflated peg-out of approximately 85,034 LTC. The issue was traced to a failure in block connection-level verification, where MWEB input metadata did not properly match the underlying UTXO being spent. While the incident briefly shook confidence in the extension layer, it was ultimately contained through coordinated miner response and rapid protocol fixes. How the MWEB exploit unfolded According to a postmortem released by Litecoin , the exploit began in March 2026 at block height 3,073,882, when an attacker successfully exploited the validation gap. By manipulating MWEB input data, the attacker made a small input appear to justify a much larger output during peg-out processing. In reality, the underlying input value was only around 1–2 LTC, but the system incorrectly accepted it as valid backing for more than 85,000 LTC. This was not a standard wallet- or transaction-layer issue. Instead, it originated in how MWEB blocks were validated during chain connection. While the mempool and transaction construction layers functioned correctly, the final consensus-level verification step failed to fully validate the integrity of MWEB metadata against the referenced outputs. Once the abnormal peg-out was detected, miners quickly identified the inconsistency and initiated coordinated action to prevent further propagation. The suspicious outputs were isolated, and a portion of the funds was frozen at the protocol level to prevent further movement across the network. Containment, recovery, and miner coordination Following detection, developers and major mining pools moved into emergency response mode. Mining pools, including F2Pool, played a central role in stabilising the network by aligning on updated validation rules and rejecting malformed MWEB data. This coordination helped prevent the exploit from spreading further across the chain. The attacker later entered negotiations and returned the majority of the exploited funds. Approximately 84,184 LTC was recovered through coordinated transactions, while an 850 LTC bounty was retained as part of the agreement in exchange for cooperation in resolving the incident. Rather than reversing the chain, developers opted for a reconciliation approach. The system effectively neutralised the inflated output by rebalancing MWEB accounting through controlled peg-in mechanisms and freezing invalid outputs. This approach allowed the network to restore consistency without requiring a full rollback. Second incident triggered a 13-block reorganisation A second related incident occurred in April 2026, when attempts to re-exploit the same vulnerability exposed a different weakness in how nodes handled malformed MWEB data. This time, the issue did not result in additional inflation but instead caused instability in node processing. Upgraded nodes experienced processing stalls when encountering mutated MWEB blocks, while some miners continued extending a chain built on outdated validation rules. This divergence led to a temporary 13-block chain reorganisation, with F2Pool mining a significant portion of the affected blocks during the unstable period. The reorganisation was short-lived. Once upgraded nodes gained majority hash power and rejected the invalid history, the network converged back to the correct chain. No permanent ledger corruption remained after reconciliation. Protocol fixes and final resolution Developers released emergency updates under the 0.21.5.x Core series, addressing both the original validation flaw and the secondary block-handling issue. The fixes strengthened MWEB input validation during block connection, improved handling of mutated block states, and reinforced consistency checks across mining and consensus layers. Post-incident analysis confirmed that the exploit did not result in lasting inflation or loss of final-chain integrity. However, it highlighted the sensitivity of extension-block systems like MWEB, where added privacy and complexity introduce new validation risks. With miner coordination restored, patched nodes deployed, and invalid outputs neutralised, the network has returned to stable operation. The post Litecoin MWEB exploit resolved, block reorganization corrected appeared first on Invezz







































