#OSINT #CyberSecurity #EthicalHacking #BugBounty #Recon
| my GitHub | https://github.com/ruyynn |
| Portfolio | https://portfolioruyynn.great-site.net/ |
| my GitHub | https://github.com/ruyynn |
| Portfolio | https://portfolioruyynn.great-site.net/ |
HTTP Request Smuggling is not just a WAF bypass trick.
Most people miss the real issue:
The vulnerability comes from differences in how HTTP requests are parsed between:
* reverse proxy (frontend)
* backend server
CL.TE / TE.CL are only the basic cases. The deeper issues are more subtle:
* HTTP/2 to HTTP/1.1 translation ambiguity
* parsing inconsistencies across proxy chains
* cache poisoning via request desynchronization
* session hijacking without traditional auth or RCE bugs
Core idea:
One request can be interpreted as two different requests depending on which layer processes it.
The exploit happens in that mismatch.
It is not an application bug in the usual sense.
It is a systemic parsing disagreement across the HTTP stack.
Top 3 on Shipit this week!
GhostIntel โ the API-free OSINT framework trusted by security pros.
Instantly extract & analyze public data like a pro.
๐ Try it now on Shipit: https://www.shipit.buzz/products/ghostintel
Or check the GitHub repo: https://github.com/ruyynn/GhostIntel
just dropped a new post about GhostIntel v2.5 ๐ป
what's new: Web UI, email breach detection, 8 countries for phone OSINT, 129+ platforms, batch processing.
still zero API keys, 100% public data.
๐ https://dev.to/ruyynn/ghostintel-v25-what-changed-since-i-first-posted-about-it-m3e
๐ป Hey #infosec folks! GhostIntel v2.5 is out ๐
Web UI for easy browsing
Email breach detection
Batch scanning across 129+ platforms
Still free, no API keys needed.
Check it out, try it, and letโs improve it together ๐
Stop using ffuf with default wordlists for directory busting.
Most companies use predictable patterns:
/api/v1/, /api/v2/
/admin/, /admin-panel/
/backup/, /backups/
Build your own wordlist from observed patterns. Results improve by 10x.
Watched 3 episodes of Mr. Robot and opened the terminal like Elliot.
Then spent the next 20 minutes googling basic Linux commands.
Hey infosec folks ๐
I built VulnDraft โ a free, open-source bug report generator.
MIT licensed โ fork it, contribute, do whatever.
What it does:
๐ H1/Bugcrowd/Intigriti templates
๐ CVSS calculator built-in
๐ Export MD, HTML, JSON
๐ป CLI + Web GUI
MIT. Open source. Free.
Try it. Break it. Tell me what sucks.
๐ https://github.com/ruyynn/VulnDraft
โญ๏ธ A star helps more people find it
Lately Iโve been thinking about what tool I should build next.
Earlier today while scrolling Facebook, I saw someone asking for help because they were confused about how to write a proper bug bounty report. They had already found the vulnerability, but didnโt know how to structure the report or present it clearly.
That got me thinking.
In bug bounty, finding the bug is one challenge โ but **writing a clear and well-structured report is another skill entirely**.
So I started considering building a small **Bug Report Generator** to help researchers quickly create structured reports with sections like summary, steps to reproduce, PoC, impact, and clean markdown output for platforms like HackerOne or Bugcrowd.
Before I start building anything, Iโm curious how other bug hunters approach reporting.
What does your ideal bug report template look like?
What sections do triagers appreciate the most?
Do you prefer minimal reports or very structured ones?
If you're a bug hunter, I'd love to hear how you write your reports.
Good reports deserve better tooling.
Hey infosec folks ๐
Iโve been working on **GhostIntel** โ a free, open-source OSINT & threat-intelligence CLI framework written in Python.
MIT licensed โ fork it, modify it, integrate it into your workflow.
The idea was simple: during investigations I kept jumping between multiple OSINT sites and tools, so I started building a CLI that could enrich indicators directly from the terminal.
Drop almost anything into GhostIntel and it will try to figure it out automatically:
โ username ยท email ยท phone ยท domain ยท IP
What it can do right now:
๐ค Username โ checks 100+ platforms in parallel
๐ฑ Phone โ carrier + region intelligence (ID ยท US ยท UK ยท MY ยท IN)
๐ง Email โ MX ยท SPF ยท DMARC ยท Gravatar ยท disposable detection
๐ Domain โ DNS records + HTTP status inspection
๐ IP โ geolocation ยท reverse DNS ยท RDAP (ARIN ยท RIPE ยท APNIC ยท LACNIC ยท AFRINIC) ยท proxy detection
๐ Reports โ export investigation results to JSON ยท HTML ยท TXT
Async-powered so lookups can run concurrently.
No API keys required.
No configuration needed.
Everything uses publicly available OSINT sources.
Built from Indonesia ๐ฎ๐ฉ for the global OSINT / infosec community.
If anyone here works in:
โข threat intelligence
โข OSINT investigations
โข SOC / DFIR
โข bug bounty research
Iโd genuinely appreciate your feedback.
โ What sources should be added?
โ What would improve your investigation workflow?
โ Anything broken or behaving weirdly?
Suggestions, criticism, and PRs are all welcome.
GhostIntel is a Python-based OSINT framework for digital investigation using public data such as username, email, domain, IP address, and phone number. - ruyynn/GhostIntel