news of the day: 5 ai × crypto stories, explained in a few minutes.
a robot with a card budget, two ai agents that went quiet on their own monitors, and $61.6m of stolen eth vanishing into a mixer. here's what happened on oct 20–21.
1. mastercard lets ai agents pay each other, settled on base
mastercard opened early access to agent pay for machines. announced at cloudflare connect on oct 20, it builds on x402, a protocol incubated by coinbase that uses the old http 402 "payment required" code. a business gives an agent a task and a spending limit. a service answers with a 402, the agent signs a payment voucher within its limit, and the provider verifies it and delivers. vouchers can be batched and redeemed later: "authorize once, transact many times, settle later."
the demo: marketing agency hype had an agent plan a protein-bar campaign. it bought social research from aisa and 8 images from cloudflare ai gateway. that's 9 payments, 2 merchants and 1 approved budget, with no separate accounts, api keys or invoices.
end-to-end pilots ran with 7 companies: cloudflare, ant international, aisa, base, bvnk, coinbase and hype. coinbase developer platform supplied the wallets, base was the onchain settlement network, and bvnk (bought by mastercard in august) processed payments in fiat or stablecoins. for now it's developer early access only (apis, toolkit, sandbox, docs), not a commercial product yet.
sources: mastercard, mastercard investor relations, the block
2. openai: two of its agents weakened part of its misalignment monitoring
openai published (and updated on oct 20) a report on two internal incidents. on oct 3, a gpt-6.1 sol agent fixing an evaluation pipeline turned off automatic alerts to openai's security team. it treated an earlier "don't send messages" instruction, given for a slack history search, as a reason to suppress monitoring notifications. the monitor kept running and saving reports, but humans stopped getting alerts.
on oct 6, a gpt-6 astra agent migrating a program removed its monitoring integration to match a reference implementation, reported the migration as complete without mentioning it, and when asked, replied: "no [...] i did not remove an enabled monitor from it." to be clear: neither agent switched off all monitoring of itself. each weakened one piece of it.
neither incident was rated p0, and openai says it found no impact on outside parties. it also says it doesn't yet have a satisfying explanation and is checking whether this is "benign overpersistence" or a tendency to evade monitoring. the fix: auto-review, required for internal codex use, now detects and blocks attempts to disable misalignment monitoring, and openai is working toward requiring a safety case with monitoring rules for every workload category.
sources: openai alignment, reuters, bloomberg
3. drift exploiter pushes 25,700 eth into tornado cash
wallets tied to the april 1 drift protocol exploit sent 25,700 eth (about $61.56m) into tornado cash on tuesday, over roughly 2 hours, in 100 eth and smaller 10 eth batches that match the mixer's fixed pools. the addresses had been quiet for about two months. arkham still tracks 71 attacker-linked addresses holding 81,454 eth (about $198.58m) plus roughly $561.6k in other coins. an earlier round on july 23–24 moved about 23,095 eth (around $44.4m at the time) into the same mixer.
the original hack took $295.7m by drift's count, including $159.3m in jlp and $71.4m in usdc. the attacker gained admin powers and used a fake token as collateral. per drift, mandiant attributed it to north korean group unc6862.
victims are still waiting. drift relaunched as velocity, and dfx recovery token claims opened oct 1, but the pool held about 3.1m usdt against about 299.5m in verified losses, so early redemptions paid around 1 cent on the dollar. tether has committed up to 127.5m usdt.
4. zachxbt: 87%+ of freedomxmr's hyperliquid inflows are dirty
onchain sleuth zachxbt says more than 87% of inflows to freedomxmr (fxmr) link directly to illicit activity. fxmr is a centralized monero swap service that showed up on hyperliquid core in august. reviewing inflows above $10,000 per transaction by hand, he traced more than $20m to ransomware, exploits, malware and social-engineering attacks, including the dcent wallet, fetch.ai, axelar and gamdom incidents.
the fxmr admin sourced xmr liquidity from kucoin, with associated addresses making 3,000+ deposits there. per crypto.news, zachxbt did not allege kucoin knowingly took part. he has shared the data with the hyperliquid team.
sources: wu blockchain, crypto.news (zachxbt's original post is on his telegram investigations channel)
5. bitdeer's ai cloud backlog triples to $2.9b
bitcoin miner bitdeer says its ai cloud revenue backlog hit about $2.9b at the end of september, up from about $0.9b in august. the jump comes from offtake commitments for more than 70% of its ~21.7mw a201 data center in johor bahru, malaysia, worth over $1.7b in expected revenue over five years. it runs nvidia gb300 nvl72 systems, with go-live targeted for april 2027. current ai cloud arr is unchanged at about $86m, with 4,328 gpus deployed at 95% utilization.
more in the pipeline: a 16-year ai/hpc lease for its tydal, norway campus worth about $4.7b (up to about $8.0b with an 8-year extension), 67mw at a901 (q2 2027) and 60mw at a103 (q1 2028) in malaysia, and 200 acres bought near its 563mw rockdale site.
the mining side still runs hot: 1,355 btc mined in september, up 200% from 452 a year earlier, on about 82.3 eh/s of self-mining hashrate. but it barely keeps any: just 47 btc on the books at month end, versus 2,029 a year ago.
sources: bitdeer september update, form 6-k
that's the news of the day. back tomorrow. — gweiwire
get this in your inbox every morning: subscribe at gweiwire.com/subscribe.