| #Hacker | #Speaker | #Mentor | #BlindGuy | #LHON | #a11y | #988 | 💀🧪⚗️ | @DeadPixelSec @NovaHackers @hacknotcrime Advocate @_MentorVillage @NextGenRedTeam
Washington DC
Joined December 2008
- Tweets17.8K
- Following3.1K
- Followers12.8K
- Likes41.9K
Pinned Tweet
Its 2025, time for a new #infosec #cybersecurity #Resume Rules Update. Things are hard out there. TImes have changed, MASSIVE layoffs'. Shrinking tech budgets and more. Here is what I got.
I. Contact Information & Online Presence:
1. Location Precision: Instead of just region, consider using a general location like "Greater [City Name] Area" or "[State] - Remote Considered." This balances privacy with giving recruiters a sense of your availability. Why: More specific than just a region, but still protects your exact address.
2. Professional Email & Portfolio Link: Use a professional email ([email address removed]) and prominently include a link to your online portfolio/personal website (if you have one). Why: Your portfolio can showcase projects, write-ups, and contributions, adding depth beyond the resume.
3. LinkedIn Profile Optimization: Ensure your LinkedIn profile is up-to-date and mirrors your resume. Use keywords strategically throughout your profile. Why: Many recruiters use LinkedIn as a primary sourcing tool.
II. Experience Section – Beyond the Technical:
4. Quantify Non-Tech Achievements: If you've held non-tech jobs, quantify your achievements there, focusing on transferable skills. For example, "Increased sales by 15% through improved customer service strategies" (demonstrates communication and problem-solving). Why: Shows you can deliver results, even outside of a purely technical environment.
5. Skill-Based Grouping: Group your experience by skill area (e.g., "Incident Response," "Vulnerability Management," "Communication & Leadership") rather than just chronological order. Within each skill area, list relevant experiences (including non-tech if applicable). Why: Highlights your expertise in key areas and makes it easier for recruiters to see your qualifications.
6. Action Verbs & Impact Statements: Start each bullet point with a strong action verb and focus on the impact of your work. Use the PAR (Problem-Action-Result) format. Why: Makes your accomplishments clear and demonstrates your value.
7. Cybersecurity in Non-Cyber Roles: If you had any cybersecurity-related responsibilities in non-tech jobs (e.g., data handling procedures, access control), emphasize these. Why: Shows initiative and interest in security, even before a formal cybersecurity role.
III. Skills & Certifications:
8. Tiered Skills Section: Create a tiered skills section. "Expert" for skills you're highly proficient in, "Proficient" for skills you're comfortable with, and "Familiar" for skills you're still learning. Why: Provides a clear picture of your skill levels and avoids overselling.
9. Certifications – Strategic Selection: List only the most relevant and in-demand certifications. Focus on those aligned with the target roles. Why: Avoids clutter and showcases the most valuable credentials.
10. Software & Tools Proficiency: List specific security tools, software, and platforms you're proficient with. Group them by category (e.g., "SIEM," "Vulnerability Scanners," "Cloud Platforms"). Why: Helps recruiters quickly identify your technical skills.
IV. Education & Projects:
11. Projects – Showcase Your Skills: Include personal projects, CTF participation, bug bounty work, or open-source contributions. Why: Demonstrates practical skills and passion for cybersecurity.
12. Education – Keep it Concise: List degrees, relevant coursework (especially if you're early in your career), and any specialized training. Why: Education is important, but experience and skills are often prioritized in cybersecurity.
V. Resume Formatting & ATS Optimization:
13. ATS-Friendly Formatting: Use a clean and simple layout. Avoid tables, images, or unusual fonts that might confuse Applicant Tracking Systems (ATS). Why: Ensures your resume gets through the initial screening process.
14. Keyword Optimization: Research relevant keywords for your target roles and incorporate them naturally throughout your resume. Why: Improves your chances of being found in ATS searches.
15. File Format: Save your resume as a PDF (.pdf). Why: Preserves formatting and is widely compatible.
16. Resume Length - Be Strategic: Aim for one page if you have less than 10 years of experience. Two pages maximum for extensive experience. Why: Keep it concise and focused on the most relevant information.
VI. Networking and Continuous Learning:
17. Networking is Key: Actively network with other cybersecurity professionals. Attend industry events, join online communities, and connect on LinkedIn. Why: Networking can open doors to unadvertised opportunities.
18. Stay Current: Cybersecurity is constantly evolving. Stay up-to-date on the latest threats, vulnerabilities, and technologies. Why: Demonstrates your commitment to professional development.
19. Tailor, Tailor, Tailor: Always tailor your resume to each specific job application. Highlight the skills and experiences that are most relevant to the target role. Why: Shows employers you understand their needs and are a good fit for the position.
VII. Networking, Continuous Learning, and Community Engagement:
20. Strategic Networking: Go beyond simply connecting on LinkedIn. Engage in meaningful conversations, offer help and insights, and build genuine relationships with other cybersecurity professionals. Why: Quality over quantity in networking.
21. Hacker Cons – Strategic Attendance: Attending relevant hacker conferences (like DEF CON, Black Hat, or local events) can demonstrate your passion and provide learning opportunities. List cons attended briefly, especially if you presented or volunteered. Why: Shows active engagement in the community.
22. Open Source Contributions: If you've contributed to open-source security projects, prominently feature this. Include links to your contributions on GitHub or other platforms. Why: Demonstrates practical coding skills and community involvement.
23. Bug Bounty Participation (Ethical): If you've participated in bug bounty programs (responsibly and ethically, of course), mention this. Quantify your findings or impact if possible. Why: Shows real-world vulnerability discovery skills.
24. Cybersecurity Community Involvement: Active participation in online forums, local meetups, or cybersecurity clubs can demonstrate your passion and knowledge. Why: Highlights your commitment to the field.
25. Mentorship (Giving Back): If you've mentored aspiring cybersecurity professionals, mention this. Why: Shows leadership and commitment to the community.
26. Personal Website/Blog (Showcase Your Expertise): Maintain a personal website or blog where you share your research, insights, or project write-ups. Include a link to it on your resume and LinkedIn profile. Why: Establishes you as a thought leader and demonstrates your knowledge.
27. Publications and Presentations: If you have published security research papers, given conference talks, or presented at meetups, list these with links if available. Why: Demonstrates deep expertise and communication skills.
Final Touches:
28. Proofread Impeccably: Have multiple people proofread your resume for any errors in grammar, spelling, or punctuation. Why: A polished resume shows attention to detail.
29. Keywords – Beyond the Basics: Go beyond simply listing keywords. Understand the context in which they are used in job descriptions and incorporate them naturally into your resume. Why: Improves ATS matching and demonstrates your understanding of the role.
30. Quantify Everything Possible: Wherever you can, quantify your achievements with numbers, percentages, or specific metrics. Why: Data speaks volumes and shows your impact.
31. "Summary/Objective" – Use Wisely: A brief summary or objective statement can be useful, especially if you're transitioning careers or have specific career goals. Tailor it to each job application. Why: Provides context and highlights your key strengths.
32. References – Available Upon Request: Don't list references directly on your resume. Simply state "References available upon request." Why: Saves space and is standard practice.
Lets keep making cybersecurity accessible to everyone. RT4<3. Be Good Do Good. #Infosecjobs #cybersecurity #Resume #linkedinopportunity #infosecurity #jobsearch #hiring #opentowork #cybersecurityjobs #infosecjobs #techjobs #careers #networking #linkedin #jobhunt
#careergoals #accessiblecybersecurity
#cybersecurityforeveryone #cybersecuritysimplified #demystifyingcybersecurity #cybersecurityexplained
Joe B. - BlindHacker retweeted
Completely agree here - You should patch PHP but the sky is not falling yet. The issue here is going to be all the IOT Crap that just does not ever get updated. There still is time to patch.
If you want to see the state of things, find a cyber range (I prefer HackTheBox). Go look for a bunch of old PHP Boxes and try the exploit out on them. Right now I think you are going to have a tough time finding a retired box that you can exploit with PHP2SHELL.... Atleast I hope you do because I am having a hell of a time doing it and both love/hate to learn how much of a noob I am at times.
AI is really good at making crap look good. I know the POC that shows a POC of <?php echo("OK") ?> being exploited sounds scary. But when you look deeper there are a lot of hard-coded offsets that make it only work on that target.
I'll be the first to admit I'm mediocre at exploit development, but I am in contact with enough extremely talented exploit developers to say this for certain:
Anyone claiming they were "easily" able to generate a working php2shell exploit with AI is either:
a) a world-class exploit developer with an extreme case of imposter syndrome.
b) currently looking at some very confident-sounding but wrong LLM output.
I'm rather certain it's the latter based on the number of AI-hallucinated exploits I've seen posted on GitHub. Threat actors are also blasting my honeypot network with "php2shell" exploits that not only don't work, but aren't even within 10,000 miles of anything to do with how the exploit actually works.
I've seen the same technique from the attached image in multiple alleged "php2shell exploits", including one on GitHub with over 100 stars. Problem is, it's not php2shell, nor is it even a vulnerability at all. It's a technique known as "session poisoning", which can be leveraged to exploit local file inclusion (LFI) vulnerabilities in PHP apps (not PHP itself).
The only thing it has in common with CVE-2026-109618/CVE-2026-109619 is they both use the "PHP_SESSION_UPLOAD_PROGRESS" feature. And mitigation advice for both issues reference setting "session.upload_progress.enabled" to "Off".
People are shoving loose details of the vulnerability into LLMs, the LLMs are keying in on the "PHP_SESSION_UPLOAD_PROGRESS" string, then generating session poisoning code that has nothing to do with the actual CVE. And because the people doing this have absolutely no idea what they're doing, they're confident enough to post their "proof of concept exploit" to GitHub and share it on social media.
So if you see people talking about "session poisoning + LFI" it's likely their LLM hallucinated an exploit based on a 2018 blog by Orange Tsai talking about a local file inclusion attack vector.
What's even worse is that "security researchers" are then using LLMs to triage these exploitation attempts, falling victim to the same hallucinations, then confirming there is ongoing mass-exploitation (there currently isn't).
The actual real exploit is very difficult to exploit, and so far I've not seen anyone successfully get it working on more than a handful of PHP version with highly-specific configurations.
LLMs are useful tools in the hands of skilled professionals, but for others, they're often just a Dunning-Kruger accelerator.
Here is a link to the Corp. Blog post on my CVE's on Edge/AI hardware and software.
I in a few weeks will drop the "hacker blog" and present on it in the 2027 season.
cobalt.io/blog/dissecting-th…
Is the flipper one still going to have a phone accessible app I cant see the small screen but I kind of want one. as long as I can operate from my mobile with screen zoom I am good,
Blind Hacker has discovered a high-severity AI supply-chain vulnerability in XXXXXXX, the primary open-source runtime powering ALL THE THINGS.
By hosting or distributing a tampered model file on public hubs (such as Hugging Face or ModelScope), an attacker can trigger arbitrary memory corruption, ASLR information disclosure, or code execution the moment an engineer or enterprise loads the model—before any AI inference or user prompt occurs.
Key Findings & Business Impact Zero-Prompt Attack Surface (Pre-Inference Execution): Unlike prompt-injection attacks which manipulate AI behavior, this is a binary exploitation defect in the host C++ inference engine. Vulnerable execution occurs immediately during model initialization (Init()) when parsing configuration metadata. Supply Chain Exploitation Model: Mirrors malicious PyTorch pickle deserialization. Any organization downloading community weights or running automated fine-tuning/conversion pipelines is exposed to host compromise.
Dual-Defect Root Cause: CWE-134 (Format String Injection): Model config path templates are passed directly as format strings to standard C library formatters, permitting arbitrary memory reads and pointer leaks. CWE-121 (Stack Buffer Overflow): Format expansion (e.g. %2000d) writes beyond a fixed 1,024-byte stack allocation, causing immediate denial-of-service or stack smashing.
Low Exploitation Complexity: Requires no authentication, no network reachability, and no specialized hardware state. A single line in a JSON configuration file triggers the defect.
Coming THOON™️
Joe B. - BlindHacker retweeted
Most AI Red Teaming or Pentesting courses teach you one or two agent exfiltration methods...
In our next version of "Attacking AI" We'll be sharing exclusive tooling (Agent-Raider) with the students that allows you to create payloads for our proprietary ~80 exfiltration techniques and channels for exploiting AI agents.
Steal data, bypass sandboxing, and pivot using these technique primitives! Agent-Raider also works with our Arcanum Prompt Injection Taxonomy as well!
Link for the next class:
arcanum-sec.com/training/att…
When writing a video game, what takes up less space, Think SMALL, floppy or cartridge style games.
Playing the sound backwards via the raw file now you have the same file one forward one back, or writing code to play it backwards?
Joe B. - BlindHacker retweeted
I haven't had any requests yet. I will mail these to you for free. No strings attached. DMs are open.
If you didn't make it to Defcon this year and want my stickers, I'm happy to mail them to you. Send me a DM with an address you want them mailed to. The large thrunting sticker is all gone, but I have the rest of them. 💜🩷💜
#HappiestHacksOnEarth
Joe B. - BlindHacker retweeted
Wake up, it's Wednesday! You know that means it's time for the 2nd Best Show on the Internet: The Wednesday Offensive!
Today we have @TheBlindHacker coming on to talk about "How I embraced the vibe hack"
See you at 130pm ET 🔗 redsiege.com/wedoff
Joe B. - BlindHacker retweeted
🔔 Friendly Neighborhood Reminder 🔔
Tomorrow on The Wednesday Offensive we'll have @TheBlindHacker leading the discussion on "How I embraced the vibe hack"
Join the conversation at 130pm ET 🔗 redsiege.com/wedoff
#hacking #infosec #cybersecurity
Hello friends,
Could you drop a follow and watch my mentee Cerd/s channel. He's talking baout some cool stuff!
youtube.com/watch?app=deskto…
Thank you!
