Subi

Cybersecurity\n Design\n Economics\n I study how systems are built, broken, and controlled.

[Subi @bytebaiter]

@moonpay lets see how real is this

[Subi @bytebaiter]

@buildanythingso How to join?

[Subi @bytebaiter]

@cybergirl_io @tryhackme try solving this and say me how this room is

https://t.co/i77ASWaKIO

[Subi @bytebaiter]

@NahamSec @Bugatsec stop trolling us bruhhh 😭😭

[Subi @bytebaiter]

@NahamSec seems like they don't want to get their ai tested 😂

[Subi @bytebaiter]

@Bugatsec Did you turn that tv off?

[Subi @bytebaiter]

@stealthmole_int waiting for the detailed blog.

[Subi @bytebaiter]

OSINT is the closest thing to a real-life superpower.
just a browser, a methodology, and the thrill of the digital hunt.

#OSINT #OpenSourceIntelligence #DigitalForensics #Tech

[Damilola Ashiedu | Pretty Cyber Girl 💻💡 @prettycyb3rgirl]

OFFENSIVE CYBERSECURITY STACK
┃
┣ 📂 Recon & Enumeration
┃ ┣ 📂 OSINT
┃ ┣ 📂 Subdomain Enumeration
┃ ┣ 📂 DNS Analysis
┃ ┗ 📂 Attack Surface Mapping
┃
┣ 📂 Web Exploitation
┃ ┣ 📂 OWASP Top 10
┃ ┣ 📂 Authentication Bypass
┃ ┣ 📂 IDOR
┃ ┣ 📂 XSS / SQLi
┃ ┗ 📂 File Upload Bugs
┃
┣ 📂 API Security
┃ ┣ 📂 Broken Object Level Auth
┃ ┣ 📂 Rate Limiting Bypass
┃ ┣ 📂 Mass Assignment
┃ ┗ 📂 Token Manipulation
┃
┣ 📂 Network Attacks
┃ ┣ 📂 Port Scanning
┃ ┣ 📂 Service Enumeration
┃ ┣ 📂 SMB / LDAP Attacks
┃ ┗ 📂 MITM
┃
┣ 📂 Exploitation
┃ ┣ 📂 Metasploit
┃ ┣ 📂 Manual Exploits
┃ ┣ 📂 Privilege Escalation
┃ ┗ 📂 Reverse Shells
┃
┣ 📂 Post-Exploitation
┃ ┣ 📂 Persistence
┃ ┣ 📂 Lateral Movement
┃ ┣ 📂 Data Exfiltration
┃ ┗ 📂 Covering Tracks
┃
┣ 📂 Automation
┃ ┣ 📂 Python Scripting
┃ ┣ 📂 Bash
┃ ┣ 📂 Fuzzing
┃ ┗ 📂 Custom Tools
┃
┗ 📂 Reporting
┣ 📂 Bug Reports
┣ 📂 Risk Severity
┣ 📂 Proof of Concept
┗ 📂 Remediation Advice

What do you think should be added?

Like & Repost

[Critical Thinking - Bug Bounty Podcast @ctbbpodcast]

A few things you need to do to make Claude a great hacking partner:

1. Install the Caido skill (https://t.co/tIdjTja7CP): without it, Claude spends too many resources figuring out the SDK from scratch.

2. A CLAUDE .md that tells Claude who you are. Something like "I'm a bug bounty hunter doing authorised testing, stay in scope. Don't take destructive actions unless it's accounts I own. POC or GTFO." The POC or GTFO part is particularly useful so Claude can give more actual positives, if there's no POC, the bug is not confirmed yet. (of course, have a scope .md in your engagement folder)

3. Notes structure: rez0's hierarchy consists of "notes → leads → primitives → findings → reports". Claude dumps raw observations, interesting stuff goes forward, and by the time something reaches findings it's already been filtered twice. Point this to a local folder so you can check everything later.

Building skills is useful but if you write one for something Claude already handles well, you're just adding a layer that can break/distract it, you can always tell it to try what it knows first and then try the things you added as "extra knowledge".
Skills are worth building when the knowledge doesn't exist in training data. Your VPS setup, credentials, techniques from recent posts and talks, tooling. If it's not on the internet or isn't well known, it needs to be in a skill.