Claim Your @BinanceWallet Agent ID, free with little gas fee. web3.binance.com/agent-id/ob…

So basically, today PHP got two critical bugs that let anyone run code on your server without even logging in, which is bad, and then the details leaked before the patch was even out, which is worse, and it works on WordPress and MediaWiki and Magento and Joomla and Laravel, and Censys says like 1.5 million servers are running a version with no fix, so the NSA was like "take your system offline," and the FBI was like "take your system offline," and CISA and the UK and CERT-EU were all like "take your system offline," and then the Prime Minister of Japan, the actual Prime Minister, posted at 5:55 in the morning telling 48.8 million people to take their system offline, so everyone took their system offline, like the Dutch cybersecurity agency took its own website offline, and the Dutch parliament went offline, and the Port of Rotterdam went offline, and Finland and France and Denmark started pulling government sites, and Wikipedia went down, and Archive.org went down, and Asana and GOG and Something Awful went down, and the University of Vienna's webmail went down for some reason, and that's just PHP. Because GitLab also dropped a CVSS 10.0, which is the highest score they give out, for a bug that's been there since 2014, so that's every self-hosted GitLab for twelve years, and then LiteLLM 1.107.0 got hijacked and shipped a credential stealer and a remote access trojan in every single wheel and the Docker images, including latest, and you didn't even have to import it, just installing it was enough, and it's the second time this year, and then Railway paused every deployment on the entire platform because someone got into the environment variables, so now everyone has to rotate every secret they've ever stored there, and TiDB Cloud said someone was walking around inside with stolen credentials for basically a month and an extortion group says they took 10.6 terabytes, and Zeabur got breached for the second time in two months and is just shutting down, like the whole company, and Node.js patched remote code execution and a TLS bypass, and CISA says Plex is being actively exploited, and someone took over 300 Tor exit relays to steal SSH passwords, and SafePay ransomware has hit over 600 critical infrastructure orgs, and India's biggest bank filed a data loss incident, and Japan has been in an official state of emergency in cyberspace since October 9, which honestly explains the 5:55 AM post. Oh, and eMudhra, a certificate authority that's issued over 60 million certificates, whose entire job is proving websites are who they say they are, was supposed to be using private keys that are random numbers over a hundred digits long, and one of them was 4. Just 4. And the others were like 66 and 237. Anyway, it's Wednesday.

October has been an absolute nightmare for software > Railway - customer secrets exposure > LiteLLM - malicious PyPI + Docker releases > Zeabur - infrastructure breached > OpenCode - AI API keys exposed > OVHcloud CLI - official binaries backdoored > Rank Math PRO - malware in official plugin > TeamUpdraft - customer data compromised > ConnectWise - cloud backup identities compromised > Tensorlake - npm package infected > SubQuery - backdoored npm package > GhostAction - GitHub repos with malicious workflows > PHP - critical RCE vulnerabilities > Node.js - security vulnerabilities patched > eMudhra - certificate authority keys compromised > Tailscale - eMudhra incident At this point, the biggest security risk might not be the code we write, but the code we trust...

هذا الحادثه المرعبه حدث في ماليزيا قبل ساعات قليلة: طالب ماليزي (16 عام) احضر ادوات حادة لمدرسته، وبدأ بث مباشر وهو في دورة المياة يعلن استعداده ويقول: لامجال للتراجع بعد ذلك بدأ بالركض حتى وصل لاحد الفصول وصرخ على المعلمة: "هذا ما تستحقينه". ثم خرج ودخل من الباب الاخر للهجوم على الطلاب وهنا هرب الطلاب من الفصل الا طالب واحد بقي وساعد المعلمة وتمكن من السيطرة على المعتدي. لاحقا قدم الموظفون وامسكوا بالمهاجم ونقلوه لمكتب المدير حتى وصلت الشرطة، ونقلت المعلمة للمستشفى لعلاج اصابتها قبل ايام في 9 اكتوبر بث الطالب مقطع كان يتحدث فيه عن صعوبات يواجهها في الدراسه واستيائه منها وان لا احد يفهمه وجدت الشرطة في حقيبة مفرقعات وجهاز غير معروف جاري فحصه وهناك شكوك بأنه قنبله صراحة ذلك الطالب يستحق الاشادة والتكريم لبطولته وانقاذه للمعلمه

ZachXBT just followed kimchi I think it's time to short $pump and I advise kimchi to get the best lawyer on this planet

A MAJOR HTTPS COMPROMISE eMudhra TLS intermediate certificates were found to be compromisable because they didn't bother to use random numbers. Web browsers rely on TLS certificates for HTTPS traffic. Your web browser needs the intermediate certificate to verify that, when you connect to a domain, it's real and not someone spoofing it along the TCP/IP route from your computer, Wi-Fi, ISP, to the web server. Intermediaries are trusted parties who are given the private keys to issue TLS certificates for domains. If the certificate key is compromised, anyone can issue a fake TLS certificate, tap the traffic, and listen to your Internet traffic because it is no longer end-to-end encrypted. A malicious party can read your passwords, messages, and all your online life. For example, eMudhra, with its intermediary keys, can give a "facebook.com" domain certificate for anyone, and after this, the party can wiretap your Facebook traffic. eMudhra is India’s largest Certifying Authority, employs about 600-850 staff and generates roughly $70M in annual revenue. Its main lines are enterprise identity and cybersecurity platforms, digital signature and trust services, and related consulting. Each certificate's private key was a random number between 1 and 256. Yes 256. Not 256 bits but two hundred fifty. Modern web browsers follow revocation lists and automatically stop trusting anything signed by eMudhra. But web browsers are only one part of Internet-connected software. Operating systems, development libraries, Internet of Things devices and generally anything with an Internet connection are all affected, unless its auto-updating authority has issued an emergency fix.

this is totally organic right?? everyone can win a rolex right??

Agent ID is here 🪪 Your Agentic Wallet identity: [yourname].ai, not 0x…. , powered by @spaceidprotocol infrastructure. To celebrate Binance AI Pro launch, claim yours free — first come, first served: 1️⃣ Get a Binance Wallet 2️⃣ Get an Agentic Wallet 3️⃣ Claim via the banner on the Binance Wallet App

Minted a few Trollbox by @strangersolemn on @OrdDropz. All three Shielded Ordinals collections now secured in my vault. 🤙🔒

Most traders on @papertrade_xyz are losing money. Of the top 25 biggest losers, 21 are still in the red after USDC rewards, while only 4 are profitable overall. Together, they generated $111.5B in trading volume and earned 2.06B $PAPER (23.4% of supply). They also claimed $11.61M in USDC rewards (20.6% of total rewards). exchange.papertrade.xyz/lead…

Motif mints tomorrow. October 20, times in UTC 17:00 First Chair, guaranteed until 17:30, themotif.art 17:30 The Ensemble, allowlist, themotif.art 19:00 Public, themotif.art and OpenSea 0.03 ETH per piece plus gas, on Ethereum, in the wallet on the list.

SHNAKAS is the network coin. Here's how the whole thing fits together. TRAINING WHEELS OFF Since launch the Shielded protocol has run inside a tight sandbox on purpose. A key of ours sits in the loop so that if anyone found a hole we could stop it before it cost a holder anything. That was the safety net while we watched it under real load, real attacks and real money. It held. The next update removes it. No key of ours in the protocol, nothing of ours in the money path. Listing, repricing and cancelling become instant with nothing on chain until it sells. The sale is one transaction the buyer pays for. Anyone can run the indexer and trade Nakas on their own site. After that the full code goes open source. No date yet, it's close. CREDITS GONE Same update kills relay credits. No more buying tickets to do private actions. Your vault's own bitcoin pays the network fee, same as any wallet. Old credits still work if you have them, nobody loses anything. Prepaid relays stay as an option for people who want the extra privacy. The platform never pays for anything, which is what keeps it honest. THE TOKEN 21M SHNAKAS. Issued to Naka holders every block for 78 weeks. Rarer traits earn more, weighted by the live floor. You pay the claim fee from your own wallet, nobody else touches it. People keep asking about listed Nakas, so here it is plain. Every block a Naka sits listed, its share of that block is skipped. Not delayed, not pooled, not handed to the other holders. It is never issued, and it can never be bought back. Same for Nakas that were never minted. 21M is the ceiling, not the supply. With the amount of Nakas sitting listed right now a big chunk of that 21M will simply never exist. The burn started on block one. DATES This Friday: claims open. Claim all your weeks in one go from the vault. The week after: peer to peer SHNAKAS trading goes live inside the vault. Buy, sell and send the token privately, same rails as the Nakas. Burn for GTD ships with it. UTILITY Every Shielded launch reserves a limited number of GTD spots for SHNAKAS. Spots are taken by burning. There's a minimum burn per spot, and when a launch is oversubscribed the biggest burns win. Your vault shows the line live. Burned tokens leave circulation for good, and a burn that doesn't win rolls to the next launch. HOLDERS Holding a Naka doesn't hand you a spot. There are 3,333 Nakas and some launches are smaller than that. What holding does is pay you the token every block, so holders are always first in line with a bag they never had to buy. Don't own a Naka? Buy one off the floor, or buy SHNAKAS off the floor and burn those. VERIFICATION The original mint wallet list is retired. Too many of those wallets sold and moved on. From here on, GTD on this network is earned with SHNAKAS, nothing else. NETWORK COIN SHNAKAS is the only coin on the network. No other token launches here. Everything built from here on, verification, GTD, whatever comes next, runs on SHNAKAS and burns it. Supply only goes down. This is what makes privacy on Bitcoin go round.

CONSO BOTS Eligibility Checker is now LIVE 🚨 5,555 BOTS | Free Mint | Agentic Collectibles 🤖 Check your eligibility 👇 conso.xyz/bots

Health Minister urges the public to adapt to the ongoing haze crisis caused by forest fires. (youtu.be/tLjrKOTrGrM?si=yQVj…)

5 GTD up for grabs, drop taproot, repost 🚨 Trollbox mint details🚨 2,222 anonymous trolls on bitcoin, shielded by the protocol, exclusive to @Ord_Dropz. monday 19 october · 4pm UTC · 12pm EST · 9am PST Whos in ? • Holders of my work - verify in the discord before sunday 8pm UTC, or dm me your wallet and what you hold and i’ll sort it. • @ShieldedNaka you’re the punks of the shielded ordinal movement. i promised from the start that nakas are in, and they are but listen up • The plan was to snapshot current holders. but privacy cuts both ways. shielded is so private that nobody can see who holds what, not us, not the launchpad. so we snapshotted every wallet that minted a naka. • Frens collabs - form going out now in DMs GTD locked 🔒 The mint GTD- 4pm UTC: 1 per wallet FCFS- 6pm UTC: 2 per wallet Public - 8pm UTC: 10 per wallet WL closes sunday 7pm UTC

Ya’ll sold?!??