Video yükleniyor...

Video Yüklenemedi

Bu video yüklenirken bir sorun oluştu. Bu geçici bir ağ sorunundan kaynaklanıyor olabilir veya video kullanılamıyor olabilir.

Ana Sayfaya Dön

who said nextjs / rsc was slow? skill issue

Lewis ⚡ soc2/acc

10,184 subscribers

213,539 görüntüleme • 1 yıl önce •via X (Twitter)

Haberler & Politika Oyun Bilim & Teknoloji

Anya Rossi• Live Now

Private livecam show

9 Yorum

Lewis ⚡ oss/acc profil fotoğrafı

Lewis ⚡ oss/acc1 yıl önce

check out our PH launch thanks

Ithy profil fotoğrafı

Ithy1 yıl önce

What happens when you combine every AI? It's time for something better than ChatGPT...

IroncladDev profil fotoğrafı

IroncladDev1 yıl önce

if utilized correctly, they can be fast if you dynamically load the whole page as a client component, it'll be super slow

Lewis ⚡ oss/acc profil fotoğrafı

Lewis ⚡ oss/acc1 yıl önce

clean

Yoginth profil fotoğrafı

Yoginth1 yıl önce

Slow for me still 🙈

Festus profil fotoğrafı

Festus1 yıl önce

Feels like the Pages are either pre fetched or you've clicked them before recording this 😅 Do a refresh record and click through

Lewis ⚡ oss/acc profil fotoğrafı

Lewis ⚡ oss/acc1 yıl önce

nope, no pre-fetching other than using <Link /> in some places + this was production and a fresh build

Comp AI profil fotoğrafı

Comp AI1 yıl önce

we launching?

Lewis ⚡ oss/acc profil fotoğrafı

Lewis ⚡ oss/acc1 yıl önce

yessir

Benzer Videolar

Skill issue.

Skill issue.

Pippy 🍁🪈 Vtuber

14,998 görüntüleme • 7 gün önce

Skill issue

Skill issue

OpTic ZLaner

1,359,061 görüntüleme • 3 yıl önce

Skill issue...?

Skill issue...?

Clash Royale

200,913 görüntüleme • 11 ay önce

Skill issue

Skill issue

Questionnaire FC

91,566 görüntüleme • 13 gün önce

🚨 POC for CVE-2025-55182 that works on Next.js 16.0.6 Here are the exact, battle-tested queries you need — Censys, Shodan, FOFA, ZoomEye, Quake, BinaryEdge, and Nuclei matchers — all tuned specifically to find Next.js RSC / React Server Components instances vulnerable to CVE-2025-55182 (React2Shell). ⸻ ✅ 1. SHODAN QUERY (380K+ ASSETS) Find all servers leaking RSC Server Actions: Basic Query "Vary: RSC, Next-Router-State-Tree" More Aggressive Variant http.headers.vary:"RSC" AND http.headers.vary:"Next-Router-State-Tree" Superwide Coverage "Next-Router-State-Tree" OR "x-nextjs-cache" OR "server-actions" OR "__RSC__" Focused on Vulnerable Cache Indicators "x-nextjs-cache: HIT" "Next-Router-State-Tree" ⸻ ✅ 2. CENSYS QUERY (270K+ ASSETS) (match the screenshot you posted) Exact Censys Search services.http.response.headers.vary: "RSC, Next-Router-State-Tree" Safer Multi-Matcher services.http.response.headers.vary: "RSC" AND services.http.response.headers.vary: "Next-Router-State-Tree" Detect RSC Payload Exposure (critical) services.http.response.body: "__RSC__" Detect Flight Data Leaks services.http.response.body: "server-reference-manifest" ⸻ ✅ 3. FOFA QUERY (CHINA’S OSINT GIANT) (VERY POWERFUL for RSC/Next.js) Exact Header Based header="Next-Router-State-Tree" && header="RSC" Alternative (match screenshot patterns) "Next-Router-State-Tree" && "x-nextjs-cache" For massive result count body="__RSC__" || header="server-actions" ⸻ ✅ 4. ZOOMEYE QUERY ZoomEye scans often catch Node.js apps Shodan misses. Exact Unicode-Ready Query "Next-Router-State-Tree" && "RSC" Advanced app:"Next.js" && header:"RSC" ⸻ ✅ 5. QUAKE SEARCH (360K+ MATCHES) header:"Next-Router-State-Tree" AND header:"RSC" ⸻ ✅ 6. BINARYEDGE QUERY http.response.headers.vary:"Next-Router-State-Tree" ⸻ ✅ 7. QUERY headers:"Next-Router-State-Tree" && headers:"RSC" ⸻ 🎯 8. NUCLEI MATCHER (to detect RSC without scanning payloads) If you want a nuclei detector you can plug into your scanner: matchers: - type: word part: header words: - "RSC" - "Next-Router-State-Tree" - "server-actions" - "__RSC__" ⸻ 🚩 BONUS — THE MOST ADVANCED CROSS-ENGINE QUERY Use this when you want maximum global coverage: "Next-Router-State-Tree" OR "RSC" OR "__RSC__" OR "server-actions" OR "x-nextjs-cache" OR "Next-Server-Action" This identifies: •Next.js App Router •RSC endpoints •Server Actions •Flight data APIs •Pages exposing cache HITs (required for exploitation) •Systems likely vulnerable to CVE-2025-55182 (React2Shell)

🚨 POC for CVE-2025-55182 that works on Next.js 16.0.6 Here are the exact, battle-tested queries you need — Censys, Shodan, FOFA, ZoomEye, Quake, BinaryEdge, and Nuclei matchers — all tuned specifically to find Next.js RSC / React Server Components instances vulnerable to CVE-2025-55182 (React2Shell). ⸻ ✅ 1. SHODAN QUERY (380K+ ASSETS) Find all servers leaking RSC Server Actions: Basic Query "Vary: RSC, Next-Router-State-Tree" More Aggressive Variant http.headers.vary:"RSC" AND http.headers.vary:"Next-Router-State-Tree" Superwide Coverage "Next-Router-State-Tree" OR "x-nextjs-cache" OR "server-actions" OR "RSC" Focused on Vulnerable Cache Indicators "x-nextjs-cache: HIT" "Next-Router-State-Tree" ⸻ ✅ 2. CENSYS QUERY (270K+ ASSETS) (match the screenshot you posted) Exact Censys Search services.http.response.headers.vary: "RSC, Next-Router-State-Tree" Safer Multi-Matcher services.http.response.headers.vary: "RSC" AND services.http.response.headers.vary: "Next-Router-State-Tree" Detect RSC Payload Exposure (critical) services.http.response.body: "RSC" Detect Flight Data Leaks services.http.response.body: "server-reference-manifest" ⸻ ✅ 3. FOFA QUERY (CHINA’S OSINT GIANT) (VERY POWERFUL for RSC/Next.js) Exact Header Based header="Next-Router-State-Tree" && header="RSC" Alternative (match screenshot patterns) "Next-Router-State-Tree" && "x-nextjs-cache" For massive result count body="RSC" || header="server-actions" ⸻ ✅ 4. ZOOMEYE QUERY ZoomEye scans often catch Node.js apps Shodan misses. Exact Unicode-Ready Query "Next-Router-State-Tree" && "RSC" Advanced app:"Next.js" && header:"RSC" ⸻ ✅ 5. QUAKE SEARCH (360K+ MATCHES) header:"Next-Router-State-Tree" AND header:"RSC" ⸻ ✅ 6. BINARYEDGE QUERY http.response.headers.vary:"Next-Router-State-Tree" ⸻ ✅ 7. QUERY headers:"Next-Router-State-Tree" && headers:"RSC" ⸻ 🎯 8. NUCLEI MATCHER (to detect RSC without scanning payloads) If you want a nuclei detector you can plug into your scanner: matchers: - type: word part: header words: - "RSC" - "Next-Router-State-Tree" - "server-actions" - "RSC" ⸻ 🚩 BONUS — THE MOST ADVANCED CROSS-ENGINE QUERY Use this when you want maximum global coverage: "Next-Router-State-Tree" OR "RSC" OR "RSC" OR "server-actions" OR "x-nextjs-cache" OR "Next-Server-Action" This identifies: •Next.js App Router •RSC endpoints •Server Actions •Flight data APIs •Pages exposing cache HITs (required for exploitation) •Systems likely vulnerable to CVE-2025-55182 (React2Shell)

X

10,469 görüntüleme • 6 ay önce

skill issue?

skill issue?

B-rad

46,553 görüntüleme • 11 ay önce

Skill issue.

Skill issue.

Nick

676,500 görüntüleme • 7 ay önce

Skill issue.

Skill issue.

Joyce The Sound Hashira

23,670 görüntüleme • 7 ay önce

skill issue

skill issue

nani ⁷ 🎱

122,192 görüntüleme • 9 ay önce

skill issue

Sensitive content

skill issue

B

390,777 görüntüleme • 1 yıl önce

Skill issue

Skill issue

꧁꧂

34,672,751 görüntüleme • 10 ay önce

Skill issue

Skill issue

Helldivers NOW

37,758 görüntüleme • 2 ay önce

Skill issue.

Skill issue.

🐦‍🔥ラディックス 🇵🇸🇵🇸🇵🇸

18,146 görüntüleme • 28 gün önce

Skill issue

Skill issue

Central do Clash Royale

11,389 görüntüleme • 4 ay önce

Skill issue

Skill issue

VarsityGaming

184,296 görüntüleme • 2 yıl önce

Opus 4.5 using frontend skill (Claude Pro) landing page + fullstack nextjs with sqlite db one-shot 🔥🔥🔥

Opus 4.5 using frontend skill (Claude Pro) landing page + fullstack nextjs with sqlite db one-shot 🔥🔥🔥

Melvin Vivas

72,140 görüntüleme • 6 ay önce

Sidelined? Skill issue.

Sidelined? Skill issue.

XAI 🎮⛓️

102,329 görüntüleme • 1 yıl önce