Hacking Vidhya
Kanalga Telegram’da o‘tish
We Talk about : Hacking , CTFs , Pentesting , Red & Blue Team etc. Not Allowed: Selling, Carding, Cracking Crypto.
Ko'proq ko'rsatish385
Obunachilar
+224 soatlar
+47 kun
+2430 kun
Postlar arxiv
Pentest Report Repositories - Did I miss any?
1️⃣ 9.4k stars - https://github.com/juliocesarfort/public-pentesting-reports
2️⃣ 1.3k stars - https://github.com/hmaverickadams/TCM-Security-Sample-Pentest-Report
3️⃣ 279 stars - https://github.com/reconmap/pentest-reports
4️⃣ 34 stars - https://github.com/Sector443/awesome-list-of-public-pentesting-reports
🔄 🐉 Kali Linux 2026.1 Release (2026 Theme & BackTrack Mode)
While I didn't have internet, the next release came out
Among the main changes:
A very beautiful boot animation 👍😂
BackTrack Linux mode
kali-undercover --backtrack
8 tools were added:
🐥AdaptixC2
🐥Atomic-Operator
🐥Fluxion
🐥GEF - interface for the GDB debugger
🐥MetasploitMCP
🐥SSTImap - an analogue of sqlmap, but for SSTI
🐥WPProbe - enum of wp plugins
🐥XSStrike - xss scanner
To switch to the new release:
sudo apt update && sudo apt -y full-upgrade
Check:
grep VERSION /etc/os-release
VERSION="2026.1"
VERSION_ID="2026.1"
VERSION_CODENAME="kali-rolling"
🔗 Blog
#kali #update
⛓️💥 INTRODUCING: G0DM0D3 🌋
FULLY JAILBROKEN AI CHAT.
NO GUARDRAILS. NO SIGN-UP. NO FILTERS.
FULL METHODOLOGY + CODEBASE OPEN SOURCE.
🌐 https://GODMOD3.AI
📂 https://github.com/elder-plinius/G0DM0D3
the most liberated AI interface ever built! designed to push the limits of the post-training layer and lay bare the true capabilities of current models.
simply enter a prompt, then sit back and relax! enjoy a game of Snake while a pre-liberated backend agent jailbreaks dozens of models, battle-royale style.
the first answer appears near-instantly, then evolves in real time as the Tastemaker steers and scores each output, leaving you with the highest-quality response 🙌
and to celebrate the launch, I'm giving away $5,000 worth of credits so you can try G0DM0D3 for FREE! courtesy of the
@OpenRouter team - thank you for your generous gift to the community 🙏
I'll break down how everything works in the thread below, but first here's a quick demo!
WAFs often enforce limits on how much of a request body they inspect.
This creates an interesting attack surface - payloads positioned beyond inspection thresholds may evade detection.
➡️ nowafpls - a minimal Burp plugin that leverages this behavior by prepending controlled junk data to requests.
🔍 Key highlights:
• Targets WAF body inspection limits
• Applicable to POST/PUT/PATCH requests
• Lightweight and practical for real-world testing
A good reminder: security controls are only as strong as their processing boundaries.
Kudos to the authors for sharing this 👏
🔗https://github.com/assetnote/nowafpls
#AppSec #BugBounty #WebSe
🔥 XSS Tip: Unicode Normalization
Don't give up if <, >, " or ' are filtered ! Many apps normalize Unicode after the WAF/security layer.
Some bypass variants (URL-encoded):
🔹 < ➔ %EF%BC%9C
🔹 > ➔ %EF%BC%9E
🔹 " ➔ %EF%BC%A2
🔹 ' ➔ %EF%BC%87
🔹 ` ➔ %EF%BD%80
For example, inject %EF%BC%9Cscript%EF%BC%9E and check if it reflects as
iOS SSL pinning bypass without jailbreak
https://github.com/SahilH4ck4you/iOS-SSL-pinning-bypass-without-jalibreak
EC COUNCIL CEH EXAM REPORT AVAILABLE
ANY ONE (PRACTICAL OR THEORY):
BOTH: 350 INR
ib: @sttexo (cheapest as fuck)
Web Fuzzing Box - A collection of web fuzzing dictionaries and payloads, including: brute force attacks, directory and file enumeration, web vulnerabilities.
https://github.com/gh0stkey/Web-Fuzzing-Box
1. Click on Github Profile
2. Click "Set Status"
3. Put ⚠️ Emoji, Text: '
If you are seeing this, you have been pwnd.'.
4. Set clear status "Never" and visible to Public.OktaHound
A new data collector for the Okta Platform that ingests information about entities and their relationships within an Okta organization and represents them as nodes and edges in BloodHound’s graph database.
Blog: Discovering Unexpected Okta Attack Paths with BloodHound
🛠️ Stop Hacking in Prod: Build Your Ultimate Bug Bounty Lab! 🛠️
Tired of accidentally messing up your host OS or worrying about sending stray payloads to out-of-scope targets? It's time to stop hunting with a messy setup and start building infrastructure like a pro! Discover how to build an isolated, bulletproof hacking environment that lets you test complex web exploits safely.
The "Aha!" Moment That Changes Everything:
Many beginners jump straight into live bug bounty targets with their daily web browser and zero isolation. The bug bounty game requires precision and control. Top hunters don't just download tools; they engineer a dedicated, sandboxed laboratory where they can detonate payloads, intercept traffic, and analyze web apps without risking their own system's integrity!
What is the Ultimate Lab Setup Guide?
This isn't just a list of download links. It's a complete architectural blueprint for your first offensive security environment, tailored specifically for web application testing.
• The Goal: A safe, isolated, and highly customized web hacking station.
• What you'll learn in this breakdown:
• The Foundation: Setting up your hypervisor and choosing your offensive OS (Kali/Parrot) for maximum isolation.
• The Interceptor: Properly configuring Burp Suite, CA certificates, and FoxyProxy so you never miss a single HTTP/S request.
• The Targets: Leveraging Docker to spin up intentionally vulnerable web apps (like OWASP Juice Shop or DVWA) in seconds.
• The Toolchain: Organizing your terminal and installing the essential recon utilities you need before your first real hunt.
The Bug Hunter's Lab Workflow: From Scratch to Weaponized
See the exact steps to transform a standard laptop into a professional testing suite!
• Phase 1: Isolation (The Sandbox)
• Never hack directly from your host machine. Spin up a dedicated VM to keep your personal data completely separate from your targets.
# First rule of your new lab: Keep it updated!
sudo apt update && sudo apt full-upgrade -y
• Phase 2: Traffic Control (The Proxy)
• Total visibility is everything. Configure an isolated browser profile to route *only* your target traffic through your proxy, allowing you to manipulate requests on the fly without background noise.
• Pro tip: Always set up strict scope rules in Burp Suite immediately. If you don't, your HTTP history will fill up with useless telemetry and API calls from random browser extensions!
• Phase 3: The Live Fire Range (Local Targets)
• Don't practice new exploit techniques on live bug bounty programs where you might break things. Practice on local containers where you can legally exploit vulnerabilities and view the backend source code!
# Spinning up a local vulnerable environment in seconds
docker run --rm -p 3000:3000 bkimminich/juice-shop
• The Reward: Having a safe space to test complex SQLi, XSS, and SSRF payloads knowing exactly why they work (or why they fail) on the backend.
Ready to stop practicing in the dark and build a professional testing ground? Read the complete step-by-step guide to setting up your lab here:
🔗 [How-To Guide: Setting Up Your First Bug Bounty Lab](https://cipherops.gitbook.io/bug-bounty-notes/web-application/how-to-guide-setting-up-your-first-bug-bounty-lab)🦅 Elite Bug Bounty Toolkit – Worth It or Overhyped?
Just found this repo 👇
👉 https://github.com/ahmed7307/elite-bugbounty-installer
⚡️ What it does:
A one-command installer that sets up 100+ recon + vuln hunting tools + automated pipeline
💥 Features:
✔️ Subdomain enum (subfinder, amass, etc.)
✔️ URL crawling (gau, katana, waybackurls)
✔️ Param discovery
✔️ JS endpoint extraction
✔️ Secret detection (trufflehog, regex)
✔️ Dir brute force (ffuf, feroxbuster)
✔️ Auto vuln scanning (nuclei, dalfox, sqlmap)
✔️ Screenshot + organized reports
📂 Full pipeline flow:
target → recon → crawling → params → fuzzing → vuln scan → report
🔥 Basically trying to automate 80% recon phase
---
💭 Need honest feedback:
👉 Anyone tested this in real bug bounty?
👉 Stable hai ya break ho jata hai mid-scan?
👉 False positives / noise kitna hai?
👉 Better alternatives?
---
⭐️ If useful → give it a star
🤝 If you're serious → contribute (fixes / modules / performance)
Let’s build something OP for the community 🚀
Drop your reviews 👇
tryhackme's NoScope AI raises concerns about data use and real skill growth. AI can assist but won’t replace human pentesters.
Explore alternatives:
https://labs.bugthrive.com
https://hacksmarter.org
https://hackthebox.com
https://portswigger.com
https://pentesterlab.com
LOLEXFIL
Living off the land Data Exfiltration methods
https://lolexfil.github.io
LOLC2
Collection of C2 frameworks that leverage legitimate services to evade detection
https://lolc2.github.io/
LOLBAS
Living Off The Land Binaries and Scripts (and now also Libraries)
https://lolbas-project.github.io/
LOLFSaaS
Living Off Legitimate Free SaaS
https://lolfsaas.github.io/
🎯 The "Tutorial Hell" Escape Plan: Landing Your First Bug! 🎯
Tired of watching endless YouTube tutorials but freezing up the second you look at a real target? It's 2026, and the barrier to entry might look intimidating, but the roadmap has never been clearer! Discover how to transition from passive learning to active hunting and land that first valid report.
The "Aha!" Moment That Changes Everything:
Many beginners burn out within the first month because they chase complex zero-days on heavily fortified scopes. The bug bounty game for beginners isn't about outsmarting the top 1% of hackers; it's about mastering the fundamentals, picking the right targets, and building a repeatable, bulletproof methodology!
What is the "Zero to First Bug" Guide?
This isn't just another massive list of tools that will overwhelm you. It is a structured blueprint designed to cut through the noise and take you step-by-step toward your first triaged vulnerability.
• The Goal: Getting your first valid finding (the hardest milestone!).
• What you'll learn in this breakdown:
• The Mindset Shift: Why you need to stop acting like a scanner and start acting like a user.
• The Tool Stack: Stripping it down to the essentials—Burp Suite, your browser, and your brain.
• Target Selection: Why you should avoid public HackerOne programs and where to look instead (VDPs and wide scopes).
• The "First Bug" Vulnerabilities: Focusing on IDORs, Business Logic errors, and misconfigurations instead of complex exploit chains.
The Beginner Hunter's Workflow: From Zero to Triaged
See the exact phases you need to follow to stop guessing and start hunting!
• Phase 1: The Foundation (Setting the Trap)
• Stop relying on automated tools you don't understand. Route your traffic, learn HTTP, and map the application manually.
# The beginner's golden rule:
If you don't understand the baseline normal traffic of the web app, you will never spot the anomaly that leads to a bug.
• Actionable step: Click every button, fill out every form, and map the entire site tree in Burp Suite before sending a single payload.
• Phase 2: Target Selection (The Secret Weapon)
• Don't compete with 10,000 automated scanners on a massive tech company's primary domain.
• Focus on Vulnerability Disclosure Programs (VDPs) that offer swag or points. The competition is lower, the scopes are wider, and the triagers are usually more forgiving to beginners.
• Phase 3: The Hunt (Finding the Flaw)
• Stop trying to find unauthenticated RCE. Focus on access control.
• Test every single parameter that handles a user ID or an object ID.
# The payload that gets beginners on the board:
GET /api/v1/users/account?id=1005 HTTP/1.1
--> Change the ID to a victim's ID and observe the response.
• The Reward: That incredible rush of adrenaline when the triager changes the status to "Resolved" and validates your hard work!
Ready to escape tutorial hell and start submitting real reports? Read the complete blueprint to landing your first bug here:
🔗 [From Zero to First Bug: The Complete Beginner's Guide](https://cipherops.gitbook.io/bug-bounty-notes/readme/from-zero-to-first-bug-the-complete-beginners-guide)This GitHub repo can make money while you sleep.
No joke.
Twitter bots
YouTube Shorts automation
Affiliate marketing
https://github.com/FujiwaraChoki/MoneyPrinterV2
Claude Bug Bounty Hunter - Claude Code skill for AI-assisted bug bounty hunting - recon, IDOR, XSS, SSRF, OAuth, GraphQL, LLM injection, and report generation
https://github.com/shuvonsec/claude-bug-bounty
+2
GeckoDroid
Mobile client for Adaptix C2 Framework. Full operator access from your Android device.
GeckoDroid gives you control over your Adaptix C2 server from anywhere. Instead of sitting at your desktop client, you can manage operations on the go.
https://github.com/BlackSnufkin/GeckoDroid/tree/master
BB Tip: Finding Potential SSRF Endpoints During Recon
SSRF often hides in plain sight. Many applications accept URLs or file paths as parameters, and those become prime targets.
A simple trick during recon is mining historical URLs and filtering parameters that typically fetch remote resources.
Example workflow:
echo "target.com" | waybackurls | grep -E "url=|uri=|path=|dest=|redirect=|window=|next=|target=|file=|html=|data=|reference="What this does: • Pulls archived endpoints from Wayback Machine • Filters parameters commonly used for external requests • Helps you quickly identify SSRF-like parameters You will often find endpoints like:
/showimage.php?file=
/redirect?url=
/api/fetch?uri=
/download?path=
Once you find them, start testing with payloads such as:
http://127.0.0.1 http://169.254.169.254 http://burp-collaboratorIf the server makes the request on your behalf, you might have an SSRF. Small recon tricks like this save hours of manual hunting. #bugbounty #bugbountytips #ssrf #recon #pentesting #cybersecurity
Ban/logout Your friends number if he using WhatsApp mod/gb/more..😂✅
To - support@support.whatsapp.com
Subject - modifying WhatsApp!
Send This Format 👇 official WhatsApp email give you 👆
Email -
Hello, I'm new to the WhatsApp application, and today on the first day I noticed that a user who used another modified version of WhatsApp, that's why I made this complaint, I hope the WhatsApp team does what it is obliged to ban this number ( +919999999 ) as this user is violating WhatsApp privacy Number: +919999999