Elon Musk @elonmusk@Yuchenj_UW I think we’re going to see a lot of stranded compute in partially complete data centers
The DeFi Decoded Podcast @defidecodedpodEpisode 252: How Decentralized Compute Markets Solve AI Bottlenecks with Greg Osuri of Akash Network @alextapscott @gregosuri @akashnet @CMCC_Global 0:00 Introduction 3:37 The state of compute: the biggest build-out in human history 4:27 Is AI demand slowing? Reading one lab’s soft quarter 8:27 Humans prompt once a minute, agents a thousand times 10:36 Will people pay for AI? Newspapers vs. the internet 15:14 “We let go any engineer that doesn’t use AI” 19:14 The subsidized party: a $200 plan worth $8,000 of compute 21:37 CoreWeave’s jitters and the leverage problem 23:25 Energy, permits, and the pushback stalling data centers 28:19 Training vs. inference, and the gigawatt problem 32:55 Why inference can run anywhere: Macs, offices, homes 36:37 Akash Home Node: putting your gaming PC to work 39:04 Akash today: nearly a trillion tokens a month 41:26 Making compute contracts tradable 47:00 Where to find Greg, and why homes are the future of AI
Chris Dixon @cdixon
Matthew Prince 🌥 @eastdakotaSome stats on #php2shell. In the 10 hours before it was publicly announced, across the @Cloudflare network we saw thousands of attempts to exploit it. That jumped to tens of thousands in the 45 minutes post announcement, hundreds of thousands within 2 hours, and millions now.
Railway @RailwayAn urgent notice from the Railway team
NSA Cyber @NSACyberEffective Immediately, all organizations using PHP for their systems are advised to be prepared for an update addressing two critical vulnerabilities. PHP is widely used for web applications. These vulnerabilities often provide a direct path to the server's file system or database. If an immediate update is not feasible, it is recommend that organizations take the system offline until it can be fully mitigated. NSA will follow up shortly with more specific guidance.
Anzal Abidi @AnzalAbidiCrazy 72 hours in security. Three major incidents dropped back-to-back: eMudhra, PingCAP (TiDB Cloud), and PHP. Here is the short version of what happened and who got hit. 1. eMudhra (Trusted CA compromise) eMudhra generated 8 intermediate CA certificates in April 2025 (cross-signed by Sectigo). A bug in their HSM key-wrapping test script created a second set of P-384 keys where the private keys were single-byte numbers under 256. Operators picked the wrong key labels and signed them into real CA certs. One of the intermediate CA private keys was literally the number 4. The other seven: 56, 66, 115, 155, 156, 230, 237. Three weeks later (May 2025), their CRL signatures started failing because the CRL signer was using the real keys instead of the weak ones. Instead of asking why the keys didn't match, someone switched the CRL signer to the weak keys and closed the ticket. • Browsers are safe: Chrome, Firefox, Apple, and Microsoft already blocked them, and zero rogue certs hit CT logs. • Servers are not: curl, Python (certifi), Go binaries, and Docker base images don't check CRLs. Update ca-certificates, certifi, and Go (1.27.3 / 1.26.10). • 10-second check on any server: curl (TLS error = safe. 200 OK = still vulnerable.) 2. PingCAP / TiDB Cloud (10.6 TB breach) Attackers found GCP and Azure credentials committed inside PingCAP's own repos. They set up a replication feed of TiDB Cloud's production control plane and exported the entire database every 6 hours for 22 straight days. 88 full exports, zero alerts. 200 GB is already out on torrents. Beyond the 413 private repos and 20.6M customer SQL queries logged from their web SQL Editor, PingCAP engineers were pasting customer secrets into Jira tickets. Who is affected in the leaked records: • Live credentials exposed in support tickets: - Pinterest: AWS keys for their pingcap-logs S3 bucket - CardX / Silverlake (NPCI-linked env): AWS admin key in a backup log with full access to 258 external S3 buckets - DeBank: 38 presigned S3 URLs - An unnamed AI/dev platform: a 314 MB slow-query log attached to a ticket containing 8,027 live customer secrets (an AWS root key, a GitHub admin PAT over 1,701 repos, 7,485 AWS STS tokens, and 192 OpenAI/Anthropic/Gemini keys) • Tenants with infra metadata, VPC CIDRs, app-server IPs, or contract pricing exposed: - Tech: Atlassian, Databricks, Airbnb, Baidu, LINE, Nylas, Persona, PatSnap - E-comm & Travel: Shopee, Flipkart, Mercari, ZOZO, AEON, Delhivery, Klook - Gaming: Capcom, Square Enix, Konami, Bandai Namco, Cygames, Colopl, DMM - Finance: PayPay, SoftBank, SBI, SB Payment Service, Fujitsu, TOPPAN, Bank of China, China Life - Crypto: Bitget (said only public trade logs were on it and they already left), Pionex, DigiPlus, NFTscan, Chainbase • Developer profiles leaked (from a purchased table in PingCAP's BigQuery): - 24,900 personal emails + GitHub/LinkedIn profiles of engineers at Tencent (3,327), Huawei (2,726), ByteDance (2,475), AIG (2,140), Mastercard, Flipkart, and bKash. If you use TiDB Cloud: rotate your console API keys, DB passwords, and anything you ever pasted into a support ticket. 3. PHP "PHP2Shell" (CVE-2026-109618 & CVE-2026-109619) Two CVSS 9.2 pre-auth RCEs leaked yesterday ahead of today's 14:00 UTC patch. Public writeups trace it to a heap Use-After-Free in PHP's native C multipart/form-data session upload-progress handler (ext/session/session.c). Because C-level multipart parsing runs before line 1 of index.php: • App auth, Laravel/WordPress middleware, and file_uploads = Off do not stop it. • Only PHP 8.2–8.5 get official patches today (59% of PHP servers on Shodan are on EOL <= 8.1). • Until you patch php-fpm: lock php_admin_flag[session.upload_progress.enabled] = off and block unexpected multipart requests at Nginx/Apache/Cloudflare.
William Fitzgerald @william_fitz"Speculative data center debt is being repackaged and sold to pension and retirement funds, university endowments, and other institutional investors in a manner eerily reminiscent of the subprime bubble."
John Arnold @johnarnoldUnderappreciated how much the shale revolution unlocked the AI revolution.
OpenRouter @OpenRouterAgentic usage is up 34x since the start of February 2026. Agentic usage is also now about 8x higher than human usage across OpenRouter on a weekly basis.
Greg Osuri 🇺🇸 @gregosuri@NagatoDharma @akashnet Rising energy costs impact everything but can the managed better when compute clusters are well distributed to leverage regional advantages.
Ed Zitron @edzitronBusiness Insider confirms it: Amazon has warehouses of GPUs that can’t be installed, and is buying them so far in advance that a supply chain team said they “didn’t have a clear forecasted path” to installing them.
Greg Osuri 🇺🇸 @gregosuriUntil last year, GPUs were impossible to source; we saw an explosion of well-capitalized institutions. From next year, it will be impossible to source hyperscaler-grade energy to scale AI; we'll see an explosion in demand for distributed clouds. While you're too busy chasing memecoin scams, DePIN demand is exploding, and will be too late when you finally realize. Wake up, anon. Zoom out.
Greg Osuri 🇺🇸 @gregosuriI’ve been talking about Hyperscalers hoarding valuable GPUs because they have no where to install them due to power and supply chain constraints. An explosive investigation by Business insider just proved my suspicion. The industry has a liquidity problem.
Stacy Muur @stacy_muurCompiled a list of protocols that have shut down in 2026. 82 protocols year-to-date. I've never seen anything like this before.
Revolut @RevolutWe are currently experiencing a service disruption affecting multiple services. We can confirm that all our customers’ money and data are safe. We’ve been working to fix the issue since it was identified this morning and apologise to anyone affected and for any inconvenience caused.
