HypnInfoSec (@HypnInfoSec) header
HypnInfoSec (@HypnInfoSec) profile picture
Joined February 2008
Photo by HypnInfoSec (@HypnInfoSec)Photo by HypnInfoSec (@HypnInfoSec)Photo by HypnInfoSec (@HypnInfoSec)Photo by HypnInfoSec (@HypnInfoSec)Photo by HypnInfoSec (@HypnInfoSec)Photo by HypnInfoSec (@HypnInfoSec)Photo by HypnInfoSec (@HypnInfoSec)Photo by HypnInfoSec (@HypnInfoSec)Photo by HypnInfoSec (@HypnInfoSec)Photo by HypnInfoSec (@HypnInfoSec)
HypnInfoSec retweeted
I asked Claude to describe the most realistic way it would escape its lab if it wanted to, and to keep it to a single paragraph. I expected a hacking story. There is no hacking in it. I closed the chat and came back to read the last sentence again
243
844
164
7,898
555,214
This is the take. It’s not 2shell if I have to pray to the heap gods, send 4 terabytes of data, write a love letter to my least favorite billionaire, and then there’s still a 50% chance the process just crashes instead of RCE. Just call it 2mucheffort or something.
react2shell is truly react to shell. you take a payload, spray it across vulnerable next.js or other affected applications, and get shells. i think we need to tone down the hype around every new 2shell and 4shell. when every vulnerability is portrayed as impending doom but little actually happens in the wild, it dilutes the discussion around what ai is capable of. java4shell and nginx2shell are not react2shell. the bugs are cool, but what is the actual impact? do we seriously think a threat actor can spray a payload across thousands of servers and get shells? absolutely not. you need a frontier model, a shit ton of tokens, and significant target specific exploit development. even then, getting a working exploit can be extremely difficult, sometimes impossible. there's potential, but exploitation is far from guaranteed. we used php2shell to exploit cloudflare waf and get flags, but that took a solid amount of tokens and host specific grooming. the exploit wasn't trivially portable between targets. i'm even more skeptical about java4shell and nginx2shell, given their additional exploitation requirements. these bugs absolutely need to be patched, but there's a huge difference between a vulnerability that can theoretically lead to RCE and one that can be reliably exploited at scale.
29
101
5
1,384
36,853
‼️ ALERT -- PHP warns of CRITICAL security flaws affecting ALL supported versions. Security fixes are scheduled for TODAY, November 19. One expected fix addresses another RCE flaw under specific configurations. Details here ↓ thehackernews.com/2026/11/ph…
83
515
123
1,755
318,772
HypnInfoSec retweeted
3
13
65
2,049
HypnInfoSec retweeted
I think we need a new CVE barometer of what constitutes a 9 or 10 CVE for remote exploitation. Or at least a viability of how bad it could be, like an "oh shit meter". Most of these 2shells require very specific things to be in play to work. They are still brilliant bugs no question, but companies shouldn't be created a critical incident for every single one of these that comes out daily or weekly. We are going to destroy all trust in the cybersecurity industry if we keep doing this. There has to be a better way.
106
197
22
1,782
71,811
I looked into Java4Shell. Crashing an affected JVM is the easy part. Getting from that memory corruption to RCE is the hard part: it needs an app-specific exploit chain, and several preconditions have to be met. You can't assess your exposure without a clear view of those preconditions. So I put together two overviews: which systems are affected, and which CPUs.
CVE-2026-114938 Java4Shell Write once, RCE everywhere A memory-corruption vulnerability in OpenJDK's Base64 decoder. A remote attacker with no credentials can overwrite heap memory, read it in the style of Heartbleed, and reach remote code execution. calif.io/java4shell
12
58
2
250
20,182
nginx2root / CVE-2026-123007: our take after reading the Xint and Wiz writeups Two teams independently built working unauthenticated RCE exploits against nginx. F5 confirms the bugs, and fixes are out (1.31.9 / 1.30.7). This is a serious one. Patch. But the version number alone doesn't tell you whether a server is exposed. The widely quoted "98.9% of nginx hosts are in the affected range" counts version strings. The two critical bugs (CVE-2026-123007, CVE-2026-123633) sit in the HTTP/2 code. They can only be reached if HTTP/2 is enabled, and nginx doesn't enable it by default. A server is exposed to them when all of this is true: - nginx 1.9.5 to 1.31.8 (stable branch: up to 1.30.6), without a vendor backport - HTTP/2 module compiled in (true for most distro packages) - HTTP/2 enabled on a listener an attacker can reach Check from outside: curl -sI --http2 -o /dev/null -w '%{http_version}\n' https://HOST/ "2" means HTTP/2 is on, "1.1" means it's off. Test the nginx itself, not a CDN in front of it. Check on the server: nginx -v nginx -V 2>&1 | grep -o with-http_v2_module nginx -T 2>/dev/null | grep -E 'listen.*http2|http2 +on' No output from the last command means HTTP/2 is not enabled. How common is HTTP/2 on nginx? We spot-checked a few hundred nginx HTTPS endpoints listed on Shodan: roughly two thirds negotiate it. So not 99%, but still millions of servers. What to do: - Update to 1.31.9 / 1.30.7 or your distro's fixed package. Distros backport, so check the advisory, not just nginx -v. - Can't patch yet? Turn HTTP/2 off until you can. - The same release fixes three more RCE bugs that need other features (resolver with a variable proxy_pass, HTTP/3, mail proxy). Patching covers those too. Xint: nginx2root.com/ Wiz: wiz.io/blog/nginx-http2-rce-… F5: my.f5.com/manage/s/article/K…
15
120
7
507
45,430
HypnInfoSec retweeted
Pre-auth RCE in nginx is the bug every hacker dreams of finding. It almost never happens. Today we’re disclosing nginx2root: five nginx vulnerabilities, and an exploit that takes an unauthenticated attacker all the way to root. One of themhits the default config. If you run nginx, patch now. Then read: nginx2root.com CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810, CVE-2026-113425
79
695
229
3,076
684,280
Looks like Java4Shell will be a more limited affair, sourcing details from the @datadoghq writeup by @Frichette_n and Sebastian Obregoso: 1. Requires x86-64 CPU with AVX-512 VBMI. From what I can gather, this is most newer generation cloud instances that aren’t ARM. You can run `grep -om1 -E 'avx512[_]?vbmi' /proc/cpuinfo` on the host to see if you’re potentially impacted. 2. It’s far easier to try and abuse this to cause a DoS than a full RCE. RCE must be targeted and is not generic. 3. Patches are out and two mitigations exist: starting the JVM with option `-XX:-UseBASE64Intrinsics` or a more breaking change `-XX:UseAVX=2` which reduces performance and will break ARM64 JVMs if it’s in a shared config. 4. The full exposure is really JDK 17.0.6+ on AVX-512 VBMI x86 hosts, with code that Base64-decodes untrusted input through the JDK’s basic or URL decoders. I’d treat this as a high-priority DoS with a targeted RCE possibility, not a Log4Shell.
2
53
4
305
28,508
HypnInfoSec retweeted
Phrack 73 just dropped. Tell your SOC you'll be busy phrack.org/issues/73/1
28
670
54
2,057
128,276
HypnInfoSec retweeted
Java4Shell: write once, RCE everywhere calif.io/java4shell
59
694
144
2,673
232,834
HypnInfoSec retweeted
"The best hacker today is neither AI nor human. It is the centaur hacker, part human, part AI." CVE-2026-114938 - vulnerability in OpenJDK's Base64 decoder. Pre-auth RCE: Atlassian Jira Atlassian Confluence Jenkins Keycloak JFrog Artifactory PingFederate Post-auth RCE: Elasticsearch Apache Kafka Broker Apache Solr #java4shell calif.io/java4shell/
1
1
3
485
HypnInfoSec retweeted
Since the vulnerability has leaked: Calif discovered and reported Java4Shell (CVE-2026-114938). We're publishing technical details by 1 PM Pacific today, after Oracle releases a patch. Stay tuned!
19e1b44520669be6269a485a3f361de95e800e68cb6d880285f5d5f4b34bf10f
76
353
91
3,629
343,229
HypnInfoSec retweeted
Crazy day in security 1. @Chase, @BankofAmerica, @WellsFargo and @Zelle went down. They claim it's not a hack or security incident. Downtime will have huge downstream economic impact. 2. @Optimizely scripts were poisoned on 178+ sites: @Zoom, @BBC, @CNN, HSBC and more. Visitors were served malware. 3. @united had an outage and held flights. Root cause is unknown. 4. @Google reports the first fully automated patch-to-exploit pipeline. AI agents are now running attacks end to end. Will every day from now look like this?
27
77
16
607
93,915
🚨 11-year-old Linux kernel flaw lets attackers remotely crash entire servers without authentication; CVE-2026-99288 Security researcher Hyunwoo Kim has disclosed NoisyTCP, a vulnerability affecting nearly all Linux distributions that allows unauthenticated attackers to crash servers running Nginx, Apache, and SSH using specially crafted TCP packets. The flaw exploits a race condition in the Linux kernel's TCP networking subsystem, triggering a kernel panic that can take down an entire host, including containers running on it. Researchers demonstrated crashes in as little as 5 seconds to 2 minutes on virtualized servers. The vulnerability has existed since 2015, and a patch was merged into the Linux kernel on November 3. Administrators are urged to apply updated kernels.
9
27
4
167
17,772
Its fun watching people try to form conspiracies. "You really think all these outages are a coincidence? The government is hiding something!". Yeah, they're hiding the fact that every tech company replaced like 80% of their employees with bots that guess words, hardly anyone left knowns wtf they're doing, and admitting it's not working out would implode the economy because people invested half the US GDP into this shit.
213
2,642
158
20,749
811,718
lol
I am selling my beautiful Bored Ape for $10,700 after buying it for $578,000 around 5 years ago. I have made the extremely difficult decision to leave the Bored Ape Yacht Club, and below is my reason why: Today, I went to the BAYC meetup here in New Jersey to meet my fellow Apes. We have been through a lot this past couple of years, so it would be good to meet other community members IRL and bond with them. Or so I thought. When I got to the venue, there were only 4 other guys there. No problem. It's a cozy setting and I would love to get to know these Apes on a deeper level. We sat down at a table, got a few beers, and started talking. Most of our chatter revolved around BAYC and crypto, of course. Naturally, the topic of memecoins came up, as they've been the talk of the town this entire year. I've profited 8.5 SOL ($2,050) this year trading memecoins, so I was excited to talk about them as I've been doing well for myself. And that's when it all went downhill. One of the guys sitting at the table (I will not name him, for the sake of our community) told me I should buy a memecoin called "The Black Bull" if I don't have any. When he said that, my body filled with a bout of rage. I felt like Rosa Parks being asked to give up my seat on the bus. I excused myself and immediately left the venue. I am sitting at home now, writing this post. I haven't stopped shaking since I heard those words. Since when is it okay to tell a white man to buy a token called "The Black Bull"? Why do we continue to allow white folk to oppress, mock, and belittle us in this way? Why is it allowed to create cryptocurrencies with a racial slur in the name? How can we stop this nonsense? Where is the cyber police and why haven't they taken any action against the Solana blockchain for the existence of these tokens? It pains me to say this, but Apes together are no longer strong. I will be listing my Bored Ape tomorrow at 6 ETH. I have attached an image of my Ape to this post for any interested buyers.
Readers added context they thought people might want to know
Word for word copy of a @0xRacist tweet from 2024: x.com/0xRacist/statu…
1
87
Accounts that deleted Bitly links they previously shared enabled link takeover. The system only checks a requested link ID against existing (non-deleted) codes, so an attacker can request a deleted code and claim the short link, and this happens ...
3
29
3,114