
Founder @YogSec | Helping Businesses Secure Their Websites | #BugBounty & #OSINT Tips - https://xitter.cf/t.co/ZemJJyfFSq | Goodness 😇
Meerut, India
Joined November 2024
- Tweets1.2K
- Following178
- Followers580
- Likes1.4K
Pinned Tweet
Join my Telegram channel for regular tips on SQLi, XSS, IDOR, enumeration & business logic bugs.
Telegram Channel: t.me/bugbountyusa
#CyberSecurity #BugBounty
MITRE ATT&CK Learning Tip
Think of it as a dictionary: ATT&CK catalogs what attackers actually do, so defenders can speak the same language. Every entry has a Tactic (goal), Technique (method), and Technique ID (e.g., T1059) for easy reference.
Learn 3 at a time: Don't memorize the whole matrix. Pick 3 techniques per week (e.g., T1059 PowerShell, T1566 Phishing, T1547 Registry Run Keys), read their real-world examples, and check if your logs would catch them.
Practice: Open ATT&CK Navigator, color the techniques you can detect the uncolored ones are your blind spots to fix.
For more tips join our Telegram channel: t.me/bugbountyusa
#MITREATTACK #ThreatHunting #InfoSec #BlueTeam #TTPs
MITRE ATT&CK Learning Tip
Think of it as a dictionary: ATT&CK catalogs what attackers actually do, so defenders can speak the same language. Every entry has a Tactic (goal), Technique (method), and Technique ID (e.g., T1059) for easy reference.
Learn 3 at a time: Don't memorize the whole matrix. Pick 3 techniques per week (e.g., T1059 PowerShell, T1566 Phishing, T1547 Registry Run Keys), read their real-world examples, and check if your logs would catch them.
Practice: Open ATT&CK Navigator, color the techniques you can detect the uncolored ones are your blind spots to fix.
For more tips join our Telegram channel: t.me/bugbountyusa
#MITREATTACK #ThreatHunting #InfoSec #BlueTeam #TTPs
Bug Bounty Tip: Path Traversal via File Signals
Look for:
File download/read params like ?file=, ?path=, ?doc=, and image/report export endpoints
Test payload: ../../../../etc/passwd - leaked file contents or changed response length confirms traversal
For more tips join our Telegram channel: t.me/bugbountyusa
#BugBounty #PathTraversal #PayloadFuzzing #InfoSec
Red teaming needs the right arsenal. My Red-Team-Tools repo curates C2 frameworks and adversary simulation resources for offensive security pros. Everything organized for real engagements.
Explore it here: github.com/yogsec/Red-Team-T…
#redteam #pentesting #cybersecurity #infosec #github
OSINT Tip: Google Dork for Finding Exposed Config and Backup Files
site:URL ("config" OR "backup" OR "credentials" OR "password") filetype:env OR filetype:bak OR filetype:log
This short OSINT dork finds exposed configuration, backup, and log files on a target domain that may contain credentials and sensitive settings. It is useful for spotting misconfigurations and data leaks during recon.
For more tips join Telegram channel t.me/bugbountyusa
#OSINT #GoogleDorks #Recon #BugBounty #InfoSec
SecretSifter is an OWASP incubator project that detects credentials exposed in browser-delivered content, not source code.
It inspects JavaScript bundles, config responses, and live traffic for secrets that only appear at build or runtime.
Ships as a Burp Suite extension, with AI triage and MCP editions available from source.
GitHub: github.com/OWASP/SecretSifte…
#OWASP #SecretScanning #AppSec #Cybersecurity #OpenSource
Check SSL/TLS configuration and find weaknesses with SSLyze
sslyze target_url
Join Bug Bounty USA Telegram channel for regular tips: t.me/bugbountyusa
#SSLyze #BugBounty #SSLSecurity #KaliLinux #WebSecurity
Bug Bounty Tip: SSTI via Template Signals
Look for:
User input reflected in rendered pages, email templates, and PDF generators — check name fields, message bodies, and report exports
Test payload: {{7*7}} - a rendered 49 in the response confirms server-side template injection
For more tips join our Telegram channel: t.me/bugbountyusa
#BugBounty #SSTI #PayloadFuzzing #InfoSec
Bug Bounty Tip: LFI via Payload Fuzzing
Look for:
File params like ?file=, ?page=, ?template=, and download endpoints
Test payload: ../../../../etc/passwd
If file contents are reflected in the response, it may indicate Local File Inclusion, enabling source code disclosure or RCE via log poisoning.
For more tips join our Telegram channel: t.me/bugbountyusa
#BugBounty #LFI #PayloadFuzzing #InfoSec
Bug Bounty Tip: Rate Limit Bypass via Header Spoofing
Look for:
POST /login or POST /send-otp returning 429 Too Many Requests.
Test by rotating headers per request: X-Forwarded-For: 1.1.1.1, X-Real-IP, X-Originating-IP, X-Client-IP, CF-Connecting-IP, True-Client-IP - or path tricks like /login, /login/, /login%00, /Login, /api/v1/login vs /api/v2/login.
If the limit resets with each spoofed value, it may indicate Rate Limit Bypass, enabling brute-force of passwords, OTPs, or coupon codes at scale.
For more tips join our Telegram channel: t.me/bugbountyusa
#BugBounty #RateLimitBypass #BruteForce #HeaderSpoofing #InfoSec
Google Dork to Find Exposed Admin Backups
Example: site:url inurl:admin ext:bak
For more tips join Telegram channel t.me/bugbountyusa
#bugbounty #googledork #recon #infosec #ethicalhacking
Bug Bounty Tip: 403 Bypass via Path Fuzzing
Look for:
GET /admin returning 403 Forbidden
Test path variations: /admin/, /admin/., /admin%2f, /admin%20, /admin..;/, /%2e/admin, /ADMIN, /admin?, /admin#, /./admin, and header tricks like X-Original-URL: /admin or X-Rewrite-URL: /admin.
If any variant returns 200 with admin content, it may indicate Access Control Bypass, enabling unauthorized access to admin panels, internal APIs, or restricted functionality.
For more tips join our Telegram channel: t.me/bugbountyusa
#BugBounty #403Bypass #AccessControl #PathFuzzing #InfoSec
For more tips join our Telegram channel: t.me/bugbountyusa
OSINT Tip: Small Google Dork for Exposed Login Pages
site:URL inurl:login OR inurl:signin OR inurl:admin
This short OSINT dork finds login and admin panels on a target domain, useful for mapping the attack surface during recon.
For more tips join Telegram channel t.me/bugbountyusa
#OSINT #GoogleDorks #LoginPages #AttackSurface #InfoSec
MITRE ATT&CK Learning Tip
Start with the matrix: ATT&CK is a map of attacker behavior. Columns = Tactics (goals like "Initial Access"), rows = Techniques (methods like "Phishing"), and sub-items = Procedures (real tools/groups using them).
Learn by scenario: Pick one attack (e.g., ransomware) and trace it across tactics — Initial Access (T1566 phishing) → Execution (T1059 PowerShell) → Persistence (T1547 registry run keys) → Exfiltration (T1041 C2 channel).
Practice: Use the free ATT&CK Navigator tool to highlight techniques seen in logs/reports and spot your detection blind spots.
For more tips join our Telegram channel: t.me/bugbountyusa
#MITREATTACK #ThreatHunting #InfoSec #BlueTeam #TTPs
Endpoints hide where the bugs live. My endpoints-extractor script pulls URLs and API endpoints from HTML, #JavaScript, and #JSON content. Built for bug bounty hunters who want deeper attack surface discovery.
Explore it here: github.com/yogsec/endpoints-…
#bugbounty #recon #pentesting #infosec #github
Black Sand Beacon is a memory-resident C2 beacon for Linux, written in C with no Go or Rust runtime.
It delivers native in-memory ELF BOF (Beacon Object File) loading, inspired by Cobalt Strike's Windows BOF model.
GitHub: github.com/grisuno/blacksand…
#C2Framework #LinuxSecurity #RedTeam #Cybersecurity #OpenSource
CVE-2026-102764
BeyondTrust Remote Support authentication bypass. Internal messaging components fail to validate message origin, allowing an unauthenticated remote attacker to perform arbitrary file operations and potentially fully compromise the appliance.
nvd.nist.gov/vuln/detail/CVE…
Find sensitive files and backups on web servers with Dirsearch
dirsearch -u URL
Join Bug Bounty USA Telegram channel for regular tips: t.me/bugbountyusa
#Dirsearch #BugBounty #DirectoryBruteforce #KaliLinux #WebSecurity
Bug Bounty Tip: XSS via Reflection Signals
Look for:
User input reflected unencoded in HTML body, attributes, or JS strings - check search boxes, profile fields, and error pages
Test payload: - an executed popup or unescaped reflection in source confirms XSS
For more tips join our Telegram channel: t.me/bugbountyusa
#BugBounty #XSS #PayloadFuzzing #InfoSec