Matt Greer

@Cyber_Sudo Is this pay once get lifetime access?

Here is a method to find someone’s email address 📧: This method only works with people who have a Pinterest account 📌. When you first create an account on Pinterest, Pinterest uses the first part of the email address you provided as your username. For example: If the email address is Saadsarraj19@gmail.com The default username on Pinterest will be: Saadsarraj19 Knowing this is very crucial ✅, as you can take the first part of the email and complete it with an email provider like @gmail.com, @hotmail.com, @outlook.com, etc. After you create a list of possible emails, you need to validate them to see which emails are active ✔️ There are multiple methods to do this, but the easiest one is by using a website like Hunter.io 🛠️ Hunter.io allows you to validate up to 50 emails/month for FREE 🎁 __________ P.S. ♻️ Repost if you found this helpful. If you liked this post and would like to learn more methods and techniques to discover information about people, check out my OSINT Mastery course cybersudo.org/osint-mastery

@nnwakelam I gave my life to Jesus in a run down parking lot almost 18 years ago. Best decision I ever made. DMs are always open if you ever wanna chat.

After seeing the ghoulish pleasure people on the left took in Charlie Kirk getting assassinated it really made me pause and consider spending more time engaging with the Christian community and faith generally. It’s still something I plan on doing that I need to make the time for.

@infinitelogins RESOURCES

I analyze thousands of bug bounty content items every month. Less than 5% makes it to the newsletter. I distilled those curated selections down to the top 25 resources for 2026 and put them in this PDF. It includes the top platforms, tools, and people that consistently deliver high signal content. Comment RESOURCES and I'll DM you the PDF for free. (Make sure your DMs are open) #BugBounty

I (and by I, I mean Claude lol) built a tool to easily output ffuf results, with regex, min/max, and include/exclude search features. I realize you can do this already with JQ, but it makes it easier IMO. github.com/DFC302/ffufr

@infinitelogins Thanks brother for the mention!

A new AI research safe harbor framework published by HackerOne and multiple new LLM-adjacent security workflows landing in the wild. On the technical side, OAuth token handling, WAF edge cases, and cloud identity misconfigurations kept showing up across write-ups . Full issue → getDisclosed.com Highlights below 👇 @Hacker0x01 introduced Good Faith AI Research Safe Harbor, an authorization and liability framework positioned for responsible AI security testing. @castilho101 shared a write-up where WAF behavior becomes part of the chain to steal Salesforce OAuth tokens and drive account takeover. @intigriti rolled out three researcher updates, an Earnings API for payout history; cross-platform reputation display; dupe resolution alerts. @albinowax posted PortSwigger hiring for on-site web and AI security researchers, tied to the PortSwigger research team. @yeswehack announced two new public programs, GoTo/GoJek with rewards up to $7,000; Zivver with rewards up to €10,000. A cURL bounty shutdown followed a flood of low-signal, apparently AI-generated reports, a sharp data point on triage load and report quality incentives. @seanhn wrote on industrialized exploit generation with agentic LLM setups, including experiments around automatic discovery and variant generation. @profundisio detailed favicon similarity search at 50M+ scale using perceptual hashing; segmented LSH indexing; CNN re-ranking. @juanurss covered practical mobile traffic interception using Frida and Burp, including SSL pinning bypass patterns and common setup pitfalls. @the_idorminator flagged GraphQL recursive query DoS testing as a resource exhaustion class, with safer probing tactics to avoid accidental outages. Trail of Bits published Claude Code skills for security research and audit workflows, modularizing LLM-assisted review into reusable components. @Jhaddix published sec-context, an AI code security anti-patterns dataset distilled from 150+ sources to steer LLM output away from unsafe patterns. @github shipped JSAnalyzer, a static JavaScript analyzer for endpoints and potential secrets, available as a Burp extension and as a Python tool. @singe released burp_global_match_replace, extending Match & Replace rules globally across Burp utilities, not only Proxy. @xnl_h4ck3r released Waymore v8.0 with GhostArchive as a source and new filtering flags, plus default behavior changes to surface more results. @caidoio shipped a browser extension for automatic proxy routing into Caido, reducing environment switching friction. @Six2dez1 highlighted Burp AI Agent updates, sessions; passive scanning; multi-provider LLM backends; issue creation and context actions. @VailSec released ffufr, a CLI for parsing and filtering FFUF JSON output to speed fuzzing triage. @dropn0w shared a recon milestone, 1M monitored live hosts across major bug bounty platforms via scanning automation. @the_idorminator shared a JavaScript hunting heuristic, grepping for .json references that point to mock response files leaking PII or secrets. @0xacb posted a compact JWT testing checklist, alg=none; weak HMAC secrets; RS256 to HS256 confusion; kid manipulation; token reuse. @0x0smilex called out CVE-2025-2294, an unauthenticated Spring SpEL RCE via gateway exposure, plus practical path and header bypass tricks. @mugh33ra shared a tiny 403 bypass payload, ";%09..", as another option for filter-based blocking probes. @rikeshbaniya highlighted a GraphQL-to-REST anti-pattern where variables interpolate into REST paths, creating traversal and internal endpoint exposure surfaces. @NahamSec published an interview on two similar 2FA bypasses reportedly totaling $70,000, centered on token and cookie handling across the login flow. @medusa_0xf demonstrated broken access control testing on feedback forms, using Burp-driven parameter swaps and escalation paths. @adnanthekhan published a Copilot Agent attack chain that exfiltrates secrets via prompt injection and a poisoned CI pipeline run. @ConspiracyProof detailed BodySnatcher, CVE-2025-12420, an auth bypass in ServiceNow Virtual Agent integrations enabling impersonation with only an email address. @OriginalSicksec analyzed account takeover paths in MCP OAuth servers, open Dynamic Client Registration; weak redirect URI validation; non-mandatory PKCE. @H4cktus showed how a leaked AWS Cognito Identity Pool ID can yield unauthenticated temporary AWS credentials when the unauth role is overly permissive. @j_domeracki published a live-bounty writeup on a privilege escalation chain using service account impersonation and token/JWT abuse in Google SecOps SOAR. @arkark_ generalized an XS-Leak oracle using ETag length as a cross-origin side-channel. Full links, writeups & more → getDisclosed.com The bug bounty world, curated.

Day FIVE of FIVE days of celebrating our 2 year ARCANUM-VERSARY! @arcanuminfosec Giveaway = FOUR seats to our ONE OF A KIND course on Pentesting and Red Teaming AI Systems: !! Attacking AI !! New giveaway rules 👀 We are pumped about a new project we released today. The likes and shares need to be applied to this post for entry! x.com/Jhaddix/status… 👍 1 Like = 1 Entry! ♻️ 1 Share = 3 Entries! (yes, THREE entries) Winners announced 1/23! Syllabus link below 👇

@rez0__ That had be a pretty cool experience! I worked for a major cable company for years and use to go into homes a lot. Saw all types of things lol.

@VailSec lollll fair. i lived in haiti for a year and ate out of open-air roadside kitchens there though... so my standards arent that high

This is a great idea lol

@BentleyAudrey I sent a connect to counteract his loss 😂

Not much has been making me laugh lately, tbh..however, I'll share with you all one thing..This guy denied my invitation to connect on LinkedIn and instead of just leaving it at that he sent me a message that said "hmmm nah" lmaaaoooo like damn

For any Christians who follow me, I think you'll love what I just put up on the blog: josephthacker.com/personal/2026/…

Day THREE of FIVE days of celebrating our 2 year ARCANUM-VERSARY! @arcanuminfosec 4th Giveaway = FOUR seats to our FLAGSHIP course on modern application assessment and recon: The Bug Hunter's Methodology! 👍 1 Like = 1 Entry! ♻️ 1 Share = 2 Entries! Winners announced 1/21! Syllabus link below 👇

Day ONE of FIVE days of celebrating our 2 year ARCANUM-VERSARY! @arcanuminfosec 2nd Giveaway - We have 4 Swag Packs up for grabs! Get a shirt, stickers, pens, a BADGE and more! 👍 1 Like = 1 Entry! ♻️ 1 Share = 2 Entries! Winners announced 1/21! enjoy our tshirt models @G0LDEN_infosec and @PhillipWylie 🫶

Happy Arcanum-versary! @arcanuminfosec 's 1st giveaway for the week is FOUR seats to our EPIC Advanced Client-Side Hacking course by myself and @xssdoctor ! 👍 1 Like = 1 Entry! ♻️ 1 Share = 2 Entries! Winners announced 1/21! Syllabus for the course below 👇

@the_IDORminator Instructions unclear. Am I supposed to be in the bathtub when I do this? 😂

Can't concentrate at work? Fill up a bath tub with warm water... Add some lavender Epsom salts... Take a deep breath... Throw your phone in the tub... Find a toaster and plug it in... Throw the toaster in the bath tub with your phone. Now relax and get back to work.

@Behi_Sec CSRF. Lol

Which vulnerability took you the longest to fully understand when you started? It took me a long time to fully understand SSRF 😅

@p0psec They are definitely still out there, just harder to find, at least for me, but I still get lucky sometimes. Lol

@VailSec Let’s go! I’m surprised those are still out there with all the automation hackers run. Congrats! 🎉

Funny, how my very first paid bug was a subdomain takeover and my first paid bug of 2026 is a subdomain takeover. I'll take it.

This week, Disclosed. (January 5, 2026) #BugBounty New MVH crowned. A million dollar WAF hardening payout, a /health endpoint turning into a credential leak, and a ZIP upload workflow producing two criticals. Full issue → getDisclosed.com Preview below 👇 @vercel detailed a $1M paid effort with @Hacker0x01 to pressure-test and harden its WAF against React2Shell-class bypasses, including runtime mitigation and detection changes. @pxmme1337 linked a newly launched anonymous forum for bug bounty discussions, with an optional verification mechanism aimed at proving bounty earnings. @Hacker0x01 announced @alexbindrei as Most Valuable Hacker of H1-3120, framed around AI security research. @Bugcrowd published a practical mapping of RCE pathways and detection methods, including command injection sinks; unsafe eval patterns; SSTI routes. @intigriti CSP bypass material focused on permissive source expressions; nonce and hash misuse; overbroad allowlists that still land script execution or exfiltration. @PortSwiggerRes published new SAML authentication bypass techniques tied to parser differentials in Ruby and PHP, including attribute pollution; namespace confusion; Void Canonicalization. @aretekzs wrote up a chain from self-XSS constraints to account takeover via DOM injection plus login CSRF and cookie-tossing effects on auth state. @xnl_h4ck3r shipped xnldorker v3.2 with Google Custom Search support and configuration changes aimed at smoother dorking workflows. @zack0x01 released video material on broken access control testing and a recon workflow overview spanning asset discovery; prioritization; validation loops. @medusa_0xf published a 2026 learning roadmap video centered on web and API hacking structure, with labs and category coverage. @ctbbpodcast dropped “2025 Hacker Stats & 2026 Goals (Ep. 155)”, reflecting on 2025 trends and predictions for 2026 workflows and disclosure dynamics. @NahamSec shared a 2025 findings retrospective video, focused on what made specific bugs interesting rather than full reproduction detail. @H4cktus published “Can you compromise a multi-billion dollar company via /health?”, centered on a health check surface exposing environment variables and sensitive cloud configuration. @_bergee_ published “Two crits, one zip”, two critical issues in a ZIP upload workflow, including symlink-based file access and a path to RCE via unsafe extraction processing. @J0R1AN walked through the Intigriti December XSS Challenge (1225), using browser behaviors like iframe messaging; performance entries; regex edge cases. @ptswarm research covered HTML-to-PDF generation stacks as a trust boundary that repeatedly turns into SSRF; local file disclosure; deserialization; DoS. This is just a preview. Full links, write-ups & more → getDisclosed.com The bug bounty world, curated.

@infinitelogins I was going to say that too lol didn't wanna jinx myself. lol.

@VailSec It's a sign, you're gonna have a great year.