Hacking Articles Tips Tricks Videos Tutorials
468 subscribers
65.9K photos
15 videos
157 files
132K links
Exploit
Pentesting
Hacking
Red Team
Blue Team
Kali Linux
Bug Bounty
Black Hat
Cyber security etc

@Hacking_Video
@Hacking_attack
Download Telegram
A Deep Dive into the Critical Vulnerability That Exposed Thousands of OrganizationsContinue reading on Medium » (https://medium.com/@VampireXRay/cve-2022-26134-the-confluence-rce-that-shook-enterprise-security-2b58c5385011?source=rss------bug_bounty-5)
How I Discovered an Information Disclosure Vulnerability in Jira Instance (CVE-2020–14179)

Hi — I’m publishing my first Medium piece, so hello, internet! This isn’t a tale of dramatic exploitation or flashy shell access. It’s a…Continue reading on Medium »
Read more...
Findomain: Essential Tool for Passive Subdomain Enumeration

Discover Findomain, a key tool in bug bounty for quick and passive subdomain recognition.Continue reading on MeetCyber »
Read more...
Hi — I’m publishing my first Medium piece, so hello, internet! This isn’t a tale of dramatic exploitation or flashy shell access. It’s a…Continue reading on Medium » (https://medium.com/@akashutosh659/how-i-discovered-an-information-disclosure-vulnerability-in-jira-instance-cve-2020-14179-644b14386e38?source=rss------bug_bounty-5)
Discover Findomain, a key tool in bug bounty for quick and passive subdomain recognition.Continue reading on MeetCyber » (https://medium.com/meetcyber/findomain-essential-tool-for-passive-subdomain-enumeration-2c1e78e71214?source=rss------bug_bounty-5)
SpiderLock: Python Web Crawler (BFS/DFS) Built for Pentesters & Recon 🕸️
https://www.reddit.com/r/Pentesting/comments/1nwv210/spiderlock_python_web_crawler_bfsdfs_built_for/

<!-- SC_OFF -->Hey everyone! I'm excited to share SpiderLock, an open-source Python web crawler I built specifically for security reconnaissance and site mapping. It's designed to give pentesters, bug bounty hunters, and security researchers a focused tool for understanding target structure. Key Features: 🔹 Supports both Breadth-First Search (BFS) and Depth-First Search (DFS) crawling strategies 🔹 Respects robots.txt before starting any crawl 🔹 Configurable depth limits for controlled exploration 🔹 Stores results in JSON for easy querying and integration 🔹 SEO Audit module for on-page optimization insights 🔹 SEO Audit module for on-page optimization insights 🔹Quick Crawl Mode for efficient high-level scans Use Cases: Pentesters performing reconnaissance during engagements Security researchers exploring target structures Developers/learners studying how crawlers work The project is fully open-source and available here: 👉 GitHub – SpiderLock (https://github.com/sherlock2215/SpiderLock) Seeking Feedback! 🙏 As I develop this further, I'd really appreciate your thoughts on: Workflow Enhancements: What features would make it more practical for your penetration testing or bug bounty workflows? Integrations: Any suggestions for other tools it should integrate with (e.g., Nmap, Gobuster, or vulnerability parsers)? Data & Visualization: Improvements to the visualization or other data export formats you'd find useful. Looking forward to your thoughts and pull requests! Happy crawling! <!-- SC_ON --> submitted by /u/Latter-Ad-8317 (https://www.reddit.com/user/Latter-Ad-8317)
[link] (https://www.reddit.com/r/Pentesting/comments/1nwv210/spiderlock_python_web_crawler_bfsdfs_built_for/) [comments] (https://www.reddit.com/r/Pentesting/comments/1nwv210/spiderlock_python_web_crawler_bfsdfs_built_for/)
Every offensive security course avl
https://www.reddit.com/r/Pentesting/comments/1nwzidt/every_offensive_security_course_avl/

<!-- SC_OFF -->If anybody wants offensive security course contents which includes pdfs and videos Contact me , i have them . I just want to help the community. <!-- SC_ON --> submitted by /u/Repulsive_Hotel555 (https://www.reddit.com/user/Repulsive_Hotel555)
[link] (https://www.reddit.com/r/Pentesting/comments/1nwzidt/every_offensive_security_course_avl/) [comments] (https://www.reddit.com/r/Pentesting/comments/1nwzidt/every_offensive_security_course_avl/)
<!-- SC_OFF -->Hi everyone, in our latest post we look under the hood of a professional-grade audio mixer to explore its security profile and consider how vulnerabilities could be leveraged by an attacker in a real world setting. <!-- SC_ON --> submitted by /u/IncludeSec (https://www.reddit.com/user/IncludeSec)
[link] (https://blog.includesecurity.com/2025/10/production-security-not-that-kind/) [comments] (https://www.reddit.com/r/Pentesting/comments/1nx98ym/production_security_not_that_kind/)
AI vs AI: How ChatGPT and I Became Bug Hunting Buddies to Find What Scanners Missed

Hey there!😁Continue reading on Medium »
Read more...
Cache Crash: How I Poisoned CDN Responses and Became Every User Simultaneously

Hey there!😁Continue reading on InfoSec Write-ups »
Read more...
Token Trouble: How Leaked JWTs Let Me Become Everyone on the Internet

Hey there!😁Continue reading on InfoSec Write-ups »
Read more...
Cowsay as a Service (CaaS) — PicoCTF Walkthrough

Cowsay as a Service (CaaS) — PicoCTF Walkthroughcowsay as a serviceHello everyone! Welcome to my very first CTF walkthrough that I’m excited to share with you today. This particular challenge stood out to me as one of the more interesting ones, and I had a great time working through it. So, without further ado, let’s dive into the solving process!Challenge Overview In this CTF challenge, we’re introduced to a quirky little web service called Cowsay as a Service (CaaS). The functionality is simple: whatever input we give in the URL, it will be displayed using the classic `cowsay` ASCII art format. For example, visiting the following URL: https://caas.mars.picoctf.net/cowsay/<message> will result in:How it works?Looks innocent, right?🕵️‍♂️ Time to Explore The key part of the challenge lies in how the user input (`{message}` in the URL) is being handled. The fact that the text we pass in gets echoed in the output hints at potential command injection. Given the use of backticks (`) is a feature in Bash command substitution, it’s worth testing to see if we can run actual shell commands through the input field. Let’s try something simple: https://caas.mars.picoctf.net/cowsay/`ls` Output:Infected input — `ls` 💥 Boom! — We just executed `ls` on the server! That means the input is being passed directly to a shell without sanitization.🏁 Finding the Flag From the directory listing above, we can see a file named `falg.txt`. It seems like a typo for `flag.txt`, but hey — CTFs love to keep us on our toes. Let’s try to read it: ``` https://caas.mars.picoctf.net/cowsay/`cat falg.txt` ``` And the result:Infected input — `cat falg.txt`🎉 Flag Captured!🎉 Flag Captured!What We LearnedAlways test how user input is handled, especially in URL paths.Command injection is a common web vulnerability — and a dangerous one if not mitigated.Bash features like command substitution (` `) can be powerful tools in CTF challenges.Final Thoughts This was a fun and lighthearted challenge that combined humor with core cybersecurity concepts. The use of `cowsay` made it a bit more entertaining than your average command injection problem, and I really enjoyed solving it.Thanks for reading, and stay tuned for more CTF walkthroughs! Cowsay as a Service (CaaS) — PicoCTF Walkthrough was originally published in InfoSec Write-ups on Medium, where people are continuing the conversation by highlighting and responding to this story.
Read more...
Errors to API Exposure

Error Based Hunting for API ExposureContinue reading on InfoSec Write-ups »
Read more...