Offensive LSO
3.27K subscribers
44 photos
20 videos
23 files
67 links
[This Channel is not intended to violate any condition of use. Copyright Disclaimer Under Section 107 of Copyright Act 1976, allowance is made for "fair use" for purposes such as criticism, comment, news reporting, teaching, scholarship, and research.]
Download Telegram
Forwarded from Red Team Village
Hi everyone,
I’m currently developing an AI-powered chatbot on Telegram focused on the field of Cyber Security.
If you’re interested in investing in this project or would like to learn more, feel free to reach out to me.
Looking forward to connecting.

@RedTeamKitBot
CloudRip Fast Cloudflare bypass scanner. A tool that helps you find the real IP addresses hiding behind Cloudflare by checking subdomains.

https://github.com/moscovium-mc/CloudRip


❤ Share & Support Us

📰 @BackupLSO
📚 @LibrarySecOfficial
📌Bug Bounty Tip: Finding Confidential Documents Fast

✅Admins often leave these unredacted files online by mistake, making them a high-medium severity finding for bug bounty programs.

❤ Share & Support Us

📰 @BackupLSO
📚 @LibrarySecOfficial
⚠️HackLabs is a collection of hands-on vulnerable labs designed to practice web exploitation, privilege escalation, Active Directory attacks, and general pentesting techniques in a safe environment.

⚠️ For educational and authorized testing only.

🔗 https://github.com/afsh4ck/HackLabs

❤ Share & Support Us

📰 @BackupLSO
📚 @LibrarySecOfficial
WAF Bypass Techniques + Tools

Here are some powerful tools and methods to help you bypass Web Application Firewalls during bug hunting:

🔥 Tools:
- wafw00f — WAF fingerprinting tool
→ https://github.com/EnableSecurity/wafw00f
- bypass-firewalls-by-DNS-history — Discover origin IPs via old DNS records
→ https://github.com/vincentcox/bypass-firewalls-by-DNS-history
- CloudFail — Excellent for bypassing Cloudflare
→ https://github.com/m0rtem/CloudFail

🔥 Effective Bypass Techniques:

1. Origin IP Discovery — Use historical DNS records (Censys, etc.) to find the real server IP and connect directly.
2. Dev/Staging Subdomains — These often don’t have WAF protection.
3. Case Variations — Try SeLeCt instead of SELECT
4. Comment Injection — SE//LECT
5. Multiple Encodings — URL → Double URL → Unicode, etc.
6. Parameter Pollution — ?id=1&id=2
7. HTTP Method Swap — Change from GET → POST → PUT
8. Content-Type Swap — Switch between form-data, JSON, XML
9. HTTP/2 Cleartext — Some WAFs only inspect HTTP/1.1

Quick WAF Detection Command:
curl -I https://target.com | grep -iE "server|cdn|cf-|x-"


Save this for your next bug bounty hunt! 🔥

❤ Share & Support Us

📰 @BackupLSO
📚 @LibrarySecOfficial
⚡Google Dorks - Cloud Storage: site:http://s3.amazonaws.com "target[.]com" site:http://blob.core.windows.net "target[.]com" site:http://googleapis.com "target[.]com" site:http://drive.google.com "target[.]com"

👉Find buckets and sensitive data.
Combine:

site:
http://s3.amazonaws.com | site:http://blob.core.windows.net | site:http://googleapis.com | site:http://drive.google.com "target[.]com"

Add something to narrow the results: "confidential” “privileged" “not for public release”

✅Credit- Mike Takahashi



Save

❤ Share & Support Us

📰 @BackupLSO
📚 @LibrarySecOfficial
url/?f=etc/passwd ==> 403
encode etc/passwd as base64

url/?f=L2V0Yy9wYXNzd2Q= ==> 200


you can use this trick in SQL , SSTI , XSS , LFI , Etc...

❤ Share & Support Us

📰 @BackupLSO
📚 @LibrarySecOfficial
Common Security Issues in Financially Oriented Web Applications

❤ Share & Support Us

📰 @BackupLSO
📚 @LibrarySecOfficial
🛡️ Bug Bounty Tip: Test IDOR + Web Cache Deception Together

When hunting IDORs, always check for web cache deception on the same endpoints:

1. As User A, access a sensitive resource like /api/invoices/123 (also try appending .css or .js).
2. As User B, repeat the exact same URL with identical headers.
3. Only change the Cookie/Auth token.

If User B receives User A's 200 OK response from cache → you've likely found a critical vulnerability!

This combo can lead to account takeover-level impacts.

❤ Share & Support Us

📰 @BackupLSO
📚 @LibrarySecOfficial
This media is not supported in your browser
VIEW IN TELEGRAM
PenTesting Agent : is an AI agent framework for black-box security testing, supporting bug bounty, red-team, and penetration testing workflows.

red team ops, Automated recon & exploitation, smart task trees, multi-agent collab, and seamless tool chaining like Nmap, Metasploit, SQLMap, Amass etc

https://github.com/GH05TCREW/pentestagent

❤ Share & Support Us

📰 @BackupLSO
📚 @LibrarySecOfficial
SQL injection.pdf
599.4 KB
🚨SQL Injection Cheat Sheet

❤ Share & Support Us

📰 @BackupLSO
📚 @LibrarySecOfficial
🔐 Testing 2FA in Web Applications?
Don’t just test the OTP.

A real 2FA assessment means checking the entire authentication flow account binding, token reuse, rate limiting, session state, backup codes, recovery flows, API logic, and more.

We turned these checks into a practical Web Pentesting Field Checklist you can keep beside you during assessments.

🎯 Built for:

• Bug Bounty Hunters
• Web Pentesters
• Security Researchers
• CTF Players

💰 Get it for just $1

Small price. Useful checklist. No unnecessary theory.

👉 Get the 2FA Bypass Field Checklist : $1

📩 To purchase, send us a message :

@LibrarySecOfficialBot
Forwarded from Library Sec Official
🤖🤖 JOIN THE Librarysec Backup COMMUNITY! 🤖🤖

Welcome to our mirrored Telegram group, designed to be a backup for our main LibrarySec Telegram channel in case of any unforeseen issues.

Stay updated with the latest in cybersecurity: e-Books, guides, market trends, wordwide analytics, industry insiders, educational resources, ethical hacking, data protection, and more.

💰 JOIN NOW! 💰

30 day's invite links

Don’t forget to stay tuned and follow us for any updates!
Forwarded from OsintGit
Hi everyone last week there was a wave of Telegram channel blocks in the OSINT community, and my second channel @osintgit was among those affected. Most channels have already been restored, but mine remains blocked. Please help forward the following message to Telegram support:
The @osintgit channel has been blocked. It contained links to articles, presentations from the author’s conference talks, and publicly available tools related to information security. The channel never published personal data or any other prohibited content. Please unblock this channel and remove the restrictions on.

Colleagues in the field have already managed to get the message through; with enough visibility we can do the same.

Please send the message to Telegram support bots:
@PressBot
@AmeliaTearheart
@BotSupport

Also use Telegram Support: Open Settings → “Ask a Question” → proceed to the question.

And email their official addresses:
dmca@telegram.org
security@telegram.org
recover@telegram.org
abuse@telegram.org
support@telegram.org

I would be grateful for reposts of this post  it greatly increases the chances of getting the channel unblocked.