Hacking Articles Tips Tricks Videos Tutorials
471 subscribers
66K 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
When developing e-commerce platforms and transaction-based web applications, engineers usually ensure that single-use assets — like…Continue reading on Medium » (https://medium.com/@t4nv1/how-a-race-condition-in-single-use-coupon-redemption-led-to-unlimited-credits-and-an-11-000-bounty-67a93a486ee0?source=rss------bug_bounty-5)
Cherry Blossom is a fun, multi-stage room that keeps you on your toes.Continue reading on Medium » (https://medium.com/@5um1t0x/cherry-blossom-tryhackme-walkthrough-f403496e1ff3?source=rss------bug_bounty-5)
Artificial intelligence is rapidly changing the way security professionals approach reconnaissance, vulnerability research, penetration…Continue reading on Medium » (https://medium.com/@pentesterclubpvtltd/agent-zero-ai-the-autonomous-ai-framework-for-cybersecurity-pentesting-ab1e6cacb544?source=rss------bug_bounty-5)
PortSwigger Lab Walkthrough — User ID Controlled by Request Parameter with Data Leakage in Redirect

Difficulty: Apprentice Category: Access Control Vulnerabilities Lab: User ID controlled by request parameter with data leakage in redirectContinue reading on Medium »
Read more...
Difficulty: Apprentice Category: Access Control Vulnerabilities Lab: User ID controlled by request parameter with data leakage in redirectContinue reading on Medium » (https://vivek0x.medium.com/portswigger-lab-walkthrough-user-id-controlled-by-request-parameter-with-data-leakage-in-redirect-21680c6506b1?source=rss------bug_bounty-5)
Red-Team-Infrastructure-Wiki
https://kitploit.com/en/tools/github/bluscreenofjeff/red-team-infrastructure-wiki

Wiki to collect Red Team infrastructure hardening resources
vegadns — Updated!
https://kitploit.com/en/posts/gitlab-wattocyber-vegadns-98175e161febf6e04d7c4b61b68bc9608c60f9fa9e5abdb057fa68608fda59b3

Rust-based DNS enumeration and subdomain discovery tool for reconnaissance and penetration testing security assessments.
sliver v1.7.6

Adversary Emulation Framework
Read more...
Httpx Explained with Practical Examples

How I use httpx to identify live hosts, collect valuable HTTP information, and streamline my bug bounty reconnaissance with practical…Continue reading on MeetCyber »
Read more...
I built a cross-platform Snaffler replacement for filesystem, network and cloud credential discovery
https://www.reddit.com/r/Pentesting/comments/1vzhuzu/i_built_a_crossplatform_snaffler_replacement_for/
How often should you run security control validation?
https://www.reddit.com/r/Pentesting/comments/1vzse1x/how_often_should_you_run_security_control/

<!-- SC_OFF -->We are building out a validation pipeline and I'm trying to decide on the cadence. We have 500+ controls mapped to CIS/NIST. A new platform we are evaluating promises to automate the "control plane" where validation results trigger updates to the controls themselves. If the validation layer tests a control, like whether our EDR blocks a specific LOLBin command, and it fails, the system triggers an automated workflow to update the EDR policy. My engineering team wants to run the full automated suite once a week to catch drift, but the SOC is pushing back because of the alert fatigue it causes. Is monthly "full sweep" with daily "spot checks" the industry standard? Or are you running continuous validation triggered by changes, such as whenever a new build is deployed? I'm trying to balance coverage with stability. <!-- SC_ON --> submitted by /u/Lowrypgztfer-Fig8398 (https://www.reddit.com/user/Lowrypgztfer-Fig8398)
[link] (https://www.reddit.com/r/Pentesting/comments/1vzse1x/how_often_should_you_run_security_control/) [comments] (https://www.reddit.com/r/Pentesting/comments/1vzse1x/how_often_should_you_run_security_control/)