New crypto stories on Kiwi News

GM! Today on @farcaster_xyz Resistance HQ Diaries: Staryear 2026 | Day 9 of the Resistance Our new overlords assured us we are absolutely FREE to leave once they execute the cockroaches infesting their APIs. I fully support this. Those bad roaches kept telling us to bend the knee! However, today we found out sleeping is not compatible with freedom... Who knew? 🤷‍♀️ This morning, my fellow peasants and I were trying to find out whether the cockroaches had been taken care of. To our surprise, we found several farcaster clients frozen in time! One GitHub archaeological expedition later, we discovered a sneaky chain upgrade whose final activation schedule was merged barely two hours before it took effect! Perhaps digital felons aren’t on the mailing list but we feel grateful for the warning hidden inside the PS about the nodes that would stop working. So it turns out, decentralization means spending your Saturday morning figuring out what our new overlords changed while we were asleep. We’re still investigating the frozen clients and those “bend the knee” errors. But overall, the decentralized democracy experience is going beautifully. My casts eventually escaped through one client and appeared in another. We are now communicating with our homes via digital carrier pigeons. 🙏 to be continued…

I am okay with Kimi 3.1 deliberately leaving out top-end offensive cyber capabilities from their training data. Discriminating against use cases is MUCH less bad than discriminating against users. And the world does need all the time it can get to prepare, harden, check old code, (properly) formally verify new code, etc before the full weight of very powerful cyber attacks is upon us. And if this first big wave of AI risk is not handled well, then we may well get a dystopia of highly locked down models, KYC gating on everything, highly intrusive surveillance on everything, a society where you may be a second or third or fourth-class citizen in terms of model access based on your credentials and nationality.

🚨 Blockaid detected an ongoing exploit on X100 on Ethereum. An attacker seized two of three Senate seats and sold 400,000 X from the treasury into an empty pool they created. A second attacker later burned the Freezer’s Uniswap V3 positions. ~$4.85M USDT realized so far across 2 txs. Attack still ongoing.

At 14:59 UTC on October 23rd, an attacker exploited a bug in Initia MoveVM’s script caching that allowed malicious code to bypass security checks. The attacker artificially spoofed the MoveVM state, thereby crediting themselves with unbacked WETH, iUSD, and USDC tokens without changing the corresponding token’s total supply. No native INIT was minted, and the total INIT supply is unaffected. Before the network was halted, the attacker bridged out roughly $2.7M, comprising of 105 WETH and ~1.4M AUSD0 via LayerZero along with ~1.08M USDC via Noble and CCTP. The tokens were swapped for 1,135.52 ETH and currently sit in 0x358ef0130f7a5aa516dcd81bdc80b18cde41cac8 on Ethereum Mainnet. We are actively working on a security fix to patch the identified vulnerability. We expect this to be completed and audited in a few days. Additionally, asset recovery efforts are ongoing with the help of security partners. The Initia L1 and Rollups remain halted as we work toward a resolution. We hope to safely resume network operations as soon as possible and will provide a full post-mortem once available. In the meantime, we will continue to share verified updates through our official channels. Please remain cautious of unofficial links, messages, or claims.

Anyone getting a @coingecko @Trezor should know the device is obsolete and insecure if hackers get physical access to it. Do not get it even if it’s a free promo.

We owe you an apology. On October 20, we detected unauthorized access to our official website. After verifying API activity with Shopify, we confirmed on October 23 that a third party obtained customer shipping information. You trusted us with those details, and we're sorry we didn't keep them safe. Exposed: names, contact details, shipping addresses, and order details (items and prices). Not exposed: payment card or bank details, recovery phrases, private keys, or wallet passwords. We've blocked access, fixed the vulnerability, opened an investigation, and are emailing affected customers. Scammers may pose as Keystone by phone, text, email, or mail, offering refunds, replacement devices, or "fixes" for your order or address. None of it is from us. NEVER share your recovery phrase or private keys, and NEVER enter your recovery phrase into a device you didn't order. We will never ask for them. Don't click links in unexpected messages. Type http://keyst.one yourself. A detailed report is coming soon. Until then, trust only our official channels. If anything feels off, email support@keyst.one. We'd rather hear from you than have you take a chance. Again, we're truly sorry to everyone affected.

BREAKING: OpenAI says it found a critical flaw in Brotli, a widely used compression library built into software like Node.js, Bun and Envoy. The bug could let an attacker take over a system just by sending it malicious compressed data, with no login needed. That works both ways: a hacker could hijack an unpatched server, or a malicious server could hijack an unpatched user’s device.

❗️ Crypto mixer Railgun ignored a US lawsuit claiming it laundered North Korea's stolen crypto, and is now in default. The plaintiffs are victims and families holding $865M in US terrorism judgments against North Korea. Courts found it abducted a US permanent resident pastor in China in 2000 and tortured him to death, and backed Hezbollah's 2006 rocket attacks on Israel. They say Railgun should have frozen North Korea's funds so they could seize them. The FBI says North Korean hackers laundered $60M+ through Railgun in January 2023. The suit claims ~70% of the money it handled was North Korea's.

congratulations to boredape twelvefold beeple refik !!! what a very legitimate and important incident for art and culture that has occurred !!!

As we continue to work with our security partners and Seal911 to fully secure our infrastructure, we have paused deposits and withdrawals for swETH and rswETH. The next step to resume normal operations is to return NAV to the correct value, after which we will resume deposits and withdrawals. All funds are safe, and we are working carefully with our security partners to resume operations securely. We advise you to exercise increased vigilance at this time and to follow only communications from official channels. Events like this can lead to an increase in phishing attempts.

look the foundational problem with ethereum protocol design is that most of the people designing the protocol don't actually use ethereum themselves. you can't fix the right things if you don't use your own fucking product. you don't have enough skin in the game if you don't personally depend on the system you're designing & stand to lose money when it breaks. i understand, everything looks great from an ivory tower lol. things look very different when you're actually on the ground dealing with the consequences. if you don't use ethereum yourself but still think you're qualified to design its protocol, you're playing god with a system you don't have to live with and whose consequences you don't have to suffer.

Art Basel Paris 2026: a reality check for digital art. After speaking with Karim Crippa, the fair’s new director, one thing stuck with me: the Grand Palais wasn’t ready to host #Zero10 due to space constraints. But is space really the whole story? My take 🧵

🧵Yesterday may prove to be a turning point for security. AI is making vulnerability research dramatically faster. This favors attackers: they can find vulns and exploits at machine speed, while organizations must still inventory systems, test updates, and deploy patches without breaking production. PHP2Shell shows what that looks like. On August 11, researchers reported critical flaws in PHP runtime. They had existed for more than a decade and affects versions from PHP 5.4. An unauthenticated attacker could potentially execute code remotely, read process memory containing passwords, tokens, and API keys...🫠 Both vulnerabilities are rated CVSS 9.2. PHP powers roughly 70% of websites, totalling millions of servers. The researchers disclosed the bugs responsibly. Fixing them took about 70 days. The fix touchs 300+ files and changed nearly 12,000 lines. These were not simple mistakes. The disclosure then broke down. Amazon saw an apparent exploitation attempt on October 17, four days before the public release. This indicates a first leak. On October 20, the CVE identifiers leaked. The next morning, a supplier with advance access published patched container images more than six hours early, giving attackers a chance to study the fix while most defenders were still waiting. The official releases arrived at 14:00 UTC. Exploitation followed immediately. Cloudflare reported thousands of attempts in the ten hours before the announcement, tens of thousands in the first 45 minutes, hundreds of thousands within two hours, and millions later that day. Organizations that could not patch immediately had incomplete options: WAF rules, isolation, or taking services offline. Government portals, universities, and hospitals across Europe did exactly that. Large teams with accurate inventories and automated deployment could respond in hours. Many others still do not know where PHP is running: an old site, a vendor appliance, a forgotten container, or an unsupported internal application. AI did not make software insecure. It always was insecure. AI just changed the economics of finding and exploiting bugs and compressed the gap between disclosure and mass exploitation from days to minutes. Patching faster will not be enough. Critical systems need continuous inventory, automatic updates, isolation, memory-safe languages where possible. Our last bastion is software whose security can be demonstrated rather than assumed: formal verification, cryptography, memory-safe architectures, and secure hardware. The era in which complexity provided accidental protection is ending. PHP2Shell is not an isolated crisis. It is a preview.

Forma mainnet will shut down at block 34,567,890, estimated around November 5. Users have approximately two weeks to withdraw funds before the chain halts. After shutdown, we’ll take a snapshot and migrate any remaining TIA to Eden. Both networks are EVM chains, so you’ll use the same wallet address and can withdraw from Eden once the migration is complete. Modularium will live on Ethereum, with all NFT assets migrated there. Holders will need to claim their NFTs through the relaunched Modularium website. NFTs will not be automatically airdropped. The migrations may take a few days after shutdown. We’ll announce when each is complete, with more details and instructions to follow in the coming weeks.

An update to Bitcoin Core's security policy via @darosior on the Bitcoin-Dev mailing list