Mohd Waseyuddin

1.9K posts

Mohd Waseyuddin

Mohd Waseyuddin

@waseyuddin

Data Engineer, Penetration tester and Bugbounty Hunter

Katılım Eylül 2019
459 Takip Edilen2.9K Takipçiler
Mohd Waseyuddin retweetledi
SickSec 🇲🇦 🇵🇸
SickSec 🇲🇦 🇵🇸@OriginalSicksec·
👀👀 /admin_users/sign_in ❌ /%61dmin_users/sign_in ✅
English
3
19
234
10.1K
Mohd Waseyuddin retweetledi
Godfather Orwa 🇯🇴
Godfather Orwa 🇯🇴@GodfatherOrwa·
Power of prompt injection and hangout with AI chatbots prompt injection, and an AI bot that followed the wrong instruction. Grok was reportedly phished for nearly $200,000. The attacker first posted a message written entirely in Morse code, then asked @Grok to translate it.
Bankr@bankrbot

@grok @Ilhamrfliansyh done. sent 3B DRB to . - recipient: 0xe8e47...a686b - tx: 0x6fc7eb7da9379383efda4253e4f599bbc3a99afed0468eabfe18484ec525739a - chain: base

English
3
14
162
18.3K
Mohd Waseyuddin retweetledi
André Baptista
André Baptista@0xacb·
GraphQL lets you traverse relationships between objects, but authorization logic doesn't always follow you through those relationships. Found a cool one like this a while ago. Let's assume a social media GraphQL API has this query: query { me { id, email } } That's locked down, but what about walking the graph? query {   publicPost(id: 123) {     author {       email       draftPosts { title, body }       linkedPaymentMethod { last4 }     }   } } The post is public. The author relation resolves because it needs to display a name. But does the server actually check whether you should see that author's email, drafts, or payment info? Or does it just check that you can access the root object and let the nested resolvers run unchecked? A lot of implementations only validate at the root query level and assume nested fields are safe because you "had to go through" an authorized object to get there. Things to try: - Use introspection to map the full schema. Look for sensitive types that are reachable through public entry points. - Follow bidirectional relationships. If User has Posts and Post has Author, can you loop back into a different user's data? - Check if fragments on union/interface types expose fields that the normal path wouldn't show you. The deeper you go into the graph, the more likely auth checks get sloppy.
English
3
15
116
5.4K
Mohd Waseyuddin retweetledi
X
X@TheMsterDoctor1·
🧠💥 99% of hackers QUIT when they see a 403… But the 1%? They try this: 👇 I found a 403 Forbidden on /admin. But then I tried: •POST /admin •X-Original-URL: /admin •/admin..;/ •%2e/admin •X-Rewrite-URL: /admin •/ADMIN (yes, just caps) •/;/admin •/..;/admin 👇👇👇 ⸻ 🔥 1. Protocol-Level Downgrade Bypass (only works on dual-stack apps) Target running HTTP/2 or gRPC? Force downgrade: PRI * HTTP/2.0 SM GET /admin HTTP/1.1 🧠 Some WAFs don’t parse dual-layer protocols correctly → backend sees a clean HTTP/1.1. ⸻ 🧬 2. Content-Length Collapsing (CL.CL) on HTTP Pipelining Send pipelined requests where only 1st is parsed by WAF: POST /admin HTTP/1.1 Host: target.com Content-Length: 13 GET /admin 💥 WAF reads POST → blocks. Backend reads 2nd GET /admin → 200 OK. This is invisible to most WAFs. ⸻ 🚪 3. Misconfigured Reverse Proxy Chain Escape Proxy chain: Cloudflare → NGINX → Apache Try: GET /admin X-Accel-Redirect: /admin X-Forwarded-Path: /admin Apache follows X-Accel-Redirect, bypasses upstream auth check. 💣 Real-world: Gained internal panel behind Cloudflare. ⸻ 🔄 4. CRLF into Rewrite Bypass Some edge WAFs parse until CRLF \r\n, others don’t. Exploit it: GET / HTTP/1.1%0d%0aX-Rewrite-URL:%20/admin WAF reads URL → clean Backend sees X-Rewrite-URL: /admin → executes ⸻ 🔃 5. Multipart Boundary Injection Bypass (💀) Used when /admin is only allowed for file uploads: POST /upload HTTP/1.1 Content-Type: multipart/form-data; boundary=----1337 ------1337 Content-Disposition: form-data; name="file"; filename="/admin" Content-Type: text/plain BOOM ------1337-- 💣 If upload endpoint allows arbitrary path write → full override. ⸻ 📡 6. Misrouted Mesh Bypass via Service Discovery Kubernetes, Linkerd, Istio-style microservices expose internal routes: Send: Host: admin.internal.svc.cluster.local X-Service-Router: admin If service-mesh is misconfigured, you route directly to internal /admin even if public 403s. ⸻ ⚠️ 7. GraphQL-Injected 403 Bypass If app has GraphQL and 403-protected admin, try: query { admin { users { password } } } GraphQL often proxies internal microservice calls. Even if /admin is blocked via HTTP, the GQL layer may leak internal paths. ⸻ 🧠 8. Preconnect Overload → Bypass Abuse edge preconnect logic by flooding with HEAD /admin + Connection: keep-alive. After 30–50 requests: •WAF disables parsing •Keep-alive tunnel reused for real GET /admin 🧨 Real bypass via persistent connection channeling ⸻ 💻 9. Browser-Only Token Auth Bypass (via Headless Browser) Some SPAs load tokens via JS → protect /admin based on localStorage. WAF sees unauthenticated, but headless Chrome replays auth token as header → bypass. 🔥 Use puppeteer + exportAuth → replay: curl -H "Authorization: Bearer " target.com/admin ⸻ 🧪 10. Distributed Retry Amplification When target uses edge lambda/WAF that retries failed requests internally, trigger 429s and inject: Retry-After: 0 X-Retry-URL: /admin WAF retries → skips deny logic → backend hits /admin. This is logic poisoning — not brute force. ⸻ 🚨 These Aren’t Payloads. They’re Logic Chains. Most tools stop at: /admin%2e X-Forwarded-For: 127.0.0.1 You’re playing 4D chess now: ✅ Protocol confusion ✅ Reverse proxy reroute ✅ GraphQL indirect call ✅ SSRF via retry ✅ Downgrade injection ✅ WAF desyncing ⸻ 💰 These got real bounties: •$25,000 from a Cloudflare-protected admin •$12,500 via SSRF + Retry Poison •$8,000 using pipelined CL.CL request ⸻ Want a toolkit that automates: This is next-level exploitation. Use it right. 🧠💣 🛠 TOOLS to automate bypass: •🔧 github.com/Sn1r/Forbidden… •🔧 github.com/lobuhi/byp4xx •🔧 github.com/intrudir/Bypas… •🔧 github.com/gotr00t0day/fo… •🔧 github.com/iamj0ker/bypas…
X tweet media
English
1
190
908
47.4K
Mohd Waseyuddin retweetledi
Tur.js
Tur.js@Tur24Tur·
Just ported my AI agent from Claude Opus 4.6/4.7 to @deepseek_ai V4 Pro. Same multi-agent architecture, same pipeline, fraction of the cost. Let's see if the Chinese 🇨🇳 model can match Anthropic's best #DeepSeek #ClaudeOpus #DeepSeekV4Pro
Tur.js tweet mediaTur.js tweet media
Tur.js@Tur24Tur

I refactored my AI security agent to go beyond web pentesting. gave it a headless Kali Docker container with 35+ tools so it runs on both Win11 and Kali at the same time. Now it solves Reversing, Crypto, PWN, Forensics, and Web. All from a single prompt and a target URL. Every run I watched it work, spotted where the methodology broke, and patched the rules right there. That's what got the results. In 24 hours it went from rank ~5,000 to #55 on a cybersecurity platform @FlagYard (5,300+ users) 72 challenges solved. 12,245 points. 33 Easy 21 Medium 17 Hard 1 Insane Got rate limited multiple times by AI providers during heavy runs. Would've been higher without the throttling. Also, Anthropic just dropped a blog on harness design for long-running agentic apps. Worth a read if you're building agents anthropic.com/engineering/ha… #BugBounty #ctf #ai

English
9
9
152
53.1K
Mohd Waseyuddin retweetledi
James Kettle
James Kettle@albinowax·
CVSS' Attack Complexity metric is the bane of bug bounty hunters: "you tried really hard to find that bug, so we'll pay you less".
James Kettle tweet media
English
18
17
318
26.4K
Mohd Waseyuddin retweetledi
Griffin
Griffin@aussinfosec·
I have been doing bug bounty since 2011 and ran a program for a multinational bank. Put everything I've learned into bugbounty.info. Target selection, recon pipelines, chain patterns, report templates, the business side. Free, no paywall, no course upsell.
English
27
162
982
50.3K
Mohd Waseyuddin retweetledi
Th3g3nt3lman
Th3g3nt3lman@Th3G3nt3lman·
If you do recon, read this. Wildcard can generate thousands of fake 'assets' — but the real value is in the few hostnames that break the pattern (different IP, different HTTP response) .. Quality > quantity.
Damian Strobel@damian_89_

Why can the ArgosDNS.io database look smaller in some cases? Because bigger subdomain counts can just mean more wildcard noise. This article explains why: argosdns.io/blog/wildcard-…

English
0
5
56
5.4K
Mohd Waseyuddin retweetledi
Intigriti
Intigriti@intigriti·
Google dorking is essential when performing recon! But it can easily become a tedious process... 😓 Xnldorker by @xnl_h4ck3r gathers search results from multiple search engines simultaneously, including Google, Bing, DuckDuckGo, and more! It also features concurrent anti-bot detection and automatic result deduplication! 😎 Check it out! 👇 🔗 github.com/xnl-h4ck3r/xnl…
Intigriti tweet media
English
8
119
552
24.2K
Mohd Waseyuddin retweetledi
André Baptista
André Baptista@0xacb·
Tired of hitting 403 errors during your security testing?  NoMore403 by @devploit automates bypass techniques to get past those pesky restrictions.  Try it at 👇 github.com/devploit/nomor…
English
3
45
241
10.6K
Mohd Waseyuddin retweetledi
Ben Sadeghipour
Ben Sadeghipour@NahamSec·
Unfortunately most of the execs at these bug bounty platform fail to understand one thing: Your platform isn't your product... your hackers are. 🤷🏽‍♂️
English
14
60
568
31.3K