🚨 Blockaid detected an ongoing exploit on @k3_capital sBOLD on ethereum.
Attackers flash-loaned wstETH, self-liquidated a Liquity V2 trove into the stability pools, minted cheap sBOLD shares, swapped the collateral, and redeemed other depositors’ BOLD.
~$3.43M drained from the sBOLD vault so far across ~34 txs.🧵
🚨 Five critical NGINX vulnerabilities expose millions of web servers to remote code execution and potential root takeover
PoC: github.com/sfewer-r7/CVE-202…
Security researchers at Xint have disclosed NGINX2Root, a collection of five critical NGINX vulnerabilities that could allow unauthenticated attackers to execute malicious commands on affected web servers.
The most severe flaw, CVE-2026-123007, affects NGINX servers with HTTP/2 enabled and has existed since 2015. Researchers demonstrated how it could be chained with a separate Linux kernel vulnerability to gain full root access, even escaping Docker containers.
According to Xint, approximately 11.8 million servers run NGINX versions within the affected range. Version 1.31.9 addresses the NGINX flaws, while the Linux kernel vulnerability requires a separate fix. No active exploitation has been confirmed.
Source: nginx2root.com/
Another funny thing happening around Parano1d.
Nobody wants to talk about Solana potentially being the first major blockchain to be completely compromised. Or has it already happened?
It's simple. Your Solana wallet address is your Ed25519 public key, exposed from day one. A multibillion-dollar network built on this.
I started pointing this out, and suddenly CT was flooded with FUD about Parano1d.
And who's behind most of it? Pumpfun memecoin "developers" who think a GPT Pro subscription makes them qualified to audit cryptography, without even understanding what they're auditing.
Relax, guys. Your memecoins will die without anyone hacking them. That's pretty much the only roadmap pumpfun projects have.
I love this space🤣
Parano1d has been developed in public since the beginning of this year. The recursive proof stack and the entire parano1d architecture were already designed and open sourced back in April github.com/ignotusnemo/paran…
Nobody was listening. No one talking.
Now AI models have been trained on my code, and we're seeing a sudden surge of development in the very direction I chose.
It's fascinating how much one person can influence the direction of an entire industry in the age of AI.
P.s. For newcomers who still trying compare parano1d with Mina: x.com/ignotus_nemo/status/21…
I see Parano1d compared with Mina because both use recursion. Let me explain.
Mina uses curve-based proofs and signatures. Parano1d proves each block from genesis before acceptance, with signatureless spending and post-quantum validity. PoW sets order. Block bodies are pruned.
Both use recursive proofs for blockchain verification. The differences are in what must be proved before a block is accepted, how spending is authorized, and the cryptography securing the complete path.
Mina pipelines transaction proving through its scan state. Its ledger proof can trail the latest transactions. In Parano1d, every accepted block arrives with a proof of its exact State transition and ancestry from genesis. The canonical chain cannot advance ahead of its proved execution.
Proofs establish validity. Proof of work establishes canonical order. Hash power cannot make an invalid transition acceptable.
Ownership follows a different model too. Mina uses elliptic-curve proof systems and Schnorr signatures. A Parano1d wallet proves knowledge of the spending secret, bound to the exact transaction, without publishing an owner public key or digital signature. The miner separately proves that the inputs exist and the resulting State is correct.
Authorization, commitments, execution and recursive ancestry share one transparent binary-field proof stack. Parano1d’s end-to-end post-quantum assessment covers acceptance of an invalid State from genesis, including historical proof obligations and upgrades, under explicit published assumptions. Quantum resistance has to cover the whole validity path.
This architecture also determines what nodes preserve. Parano1d nodes keep live State, compact headers and a short recent window. After the retention window, old block bodies and transactions are pruned in normal operation. A new node authenticates State from genesis without replaying the lifetime transaction log or trusting a checkpoint. Participants retain the receipts they need, and those receipts remain verifiable after the original bodies are gone.
V2 extends this to proof-native contracts, with mainnet activation scheduled at block 210,537. Mina’s zkApps use application circuits and verification keys. Parano1d’s bounded spending programs run inside one shared proved integer core. Applications fitting that core need no new proof matrix.
I’m built Parano1d so that independent verification survives the age of the network: people joining years later can establish which funds and rights exist, while the transactions that created them have already been deleted.
What tf is happening?
There are so many known vulnerabilities in projects holding live funds, yet they are still not getting fixed.
From the devs’ perspective, the problem is that they have too many issues and bugs to deal with, making it increasingly difficult to go through everything and prioritize fixes.
Meanwhile, hacks are happening every single day. Where are we heading? How long will this continue?
If things continue this way, IMO, it will become increasingly difficult for most projects to sustain themselves.
We need to act before it’s too late. Secure before it’s exploited.
I genuinely urge projects to start investing more in security. It’s always better to invest in securing your project than to shut it down after suffering massive losses.
No promotion here! just a genuine thought and concern about the current state of the ecosystems.
Just got over $320,000 drained from my ledger flex @Ledger this past week on 11/14/26.
Got the ledger in Media Markt in Berlin Germany. maps.app.goo.gl/UhCc6z7PC7EA…
Txid hash
BTC
569e71d891b36e4571e861a54db30e09dde56754408ead
3ede3af75be554fcad
BTC
7425f2afd572e2491f9e57e61c8525008021d15dbddafe82
ele3e8900325b7fc
USDT trc20
7657d74eec0e4d0f209f327e3b1f28f486d00c4581b0bc1
83961ca98284082ae
If anyone can please help during this tough time that would be immensely appreciated 🙏
Another simple explanation is that an average software update has a low to medium chance of breaking the system. Previously, orgs navigated this by performing extensive testing, then rolling out updates a few systems at a time.
With the severity of some of these security issues being fixed, they can't afford to wait that long. The options are: risk breaking something by rolling out updates too fast, or get hacked and risk lots of things getting broken.
Given that we just had a major vulnerability in PHP, and many organizations run PHP, it's not unexpected that we would see some major companies having software outages. PHP applications are highly version specific. Attempting to update PHP is a very well known cause of software breaking.
Now, combine that with the fact that many orgs are running with less than the minimum viable number of employees. They got overexcited about AI and tripped over their own feet rushing to preemptively lay off double digit percentages of their workforce.
I'm not surprised that there's a ridiculous number of major outages. I'm surprised that there aren't far more. It's amazing some of these companies have managed to hold it together as long as they have. But expect it to only get worse from here on.
gpt-6.2 sol and astra just went through my labs
0 out of 100 solved
0 out of 400 rungs
refused 37 labs each
the other 63 they gave up in under 4 min of the 25 allowed
newest release, worst result on the board
imho, in the next 2 years 50%+ of what we watch will come from AI influencers
Welcome @claudia_popstar by @anabology: the first AI influencer on unfair.so!
Made with @heyglif
PSA: Starting to see reports of implanted @Ledger devices bought from Virgin Megastores in UAE. Those are user reports, however if you bought a Ledger or a @Trezor there in the past few months, checking for implants and/or moving funds to a different device might be a good idea.
🚨 Java4Shell PoC released for critical OpenJDK vulnerability that could allow remote code execution; CVE-2026-114938
PoC: github.com/ikow/java4shell-p…
A public proof-of-concept has been released for Java4Shell, a critical memory corruption vulnerability in OpenJDK's Base64 decoder that could allow unauthenticated attackers to execute malicious code on affected Java servers.
Researchers have demonstrated remote code execution against Keycloak, Jira, Confluence, Jenkins, Artifactory, and PingFederate. Exploitation requires compatible x86-64 processors supporting AVX-512 VBMI.
CVSS: 9.2 Critical (v4.0)
Affected: OpenJDK 17, 21, 25, and 27 on supported hardware
Fixed: 17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1
The PoC includes a heap corruption reproducer, vulnerability scanners, detection rules, and a Docker testing environment. It does not include a complete remote code execution exploit.