home.social

#bugbounty — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #bugbounty, aggregated by home.social.

  1. Just heard someone's #HotTake (tm) that the age of #AI and #LLMs will cause corporate #BugBounty programs to dramatically lose value. This will result in a surplus of highly skilled #hackers with no work or income.

    And in my mind, this sounds exactly like 18th century privateers and I'm now wondering if this will be an #AssassinsCreed title in 200 years time... 😂

    #InfoSec #CyberSec #funny

  2. Advanced Subdomain Discovery with Amass and Cheat Sheet

    In this cheat sheet, I cover essential Amass commands, enumeration techniques, and practical workflows for effective recon.
    denizhalil.com/2026/05/02/owas

    #CyberSecurity #OWASP #Amass #SubdomainEnumeration #Recon #OSINT #AttackSurface #BugBounty

  3. Advanced Subdomain Discovery with Amass and Cheat Sheet

    In this cheat sheet, I cover essential Amass commands, enumeration techniques, and practical workflows for effective recon.
    denizhalil.com/2026/05/02/owas

    #CyberSecurity #OWASP #Amass #SubdomainEnumeration #Recon #OSINT #AttackSurface #BugBounty

  4. Advanced Subdomain Discovery with Amass and Cheat Sheet

    In this cheat sheet, I cover essential Amass commands, enumeration techniques, and practical workflows for effective recon.
    denizhalil.com/2026/05/02/owas

    #CyberSecurity #OWASP #Amass #SubdomainEnumeration #Recon #OSINT #AttackSurface #BugBounty

  5. 🎖️ El Curso de Maltego Graph CE está permanente disponible en el aula virtual para acceso inmediato. 📲 WhatsApp: https://wa.me/51949304030 🌐 https://www.reydes.com/e/Curso_Maltego #cyberthreatintelligence #threatintel #cybersecurity #investigation #cyberinvestigation #bugbounty #osint
  6. Day 5 — CSRF Token Bypass using GET Request
    This article discusses a Cross-Site Request Forgery (CSRF) vulnerability where an attacker can bypass CSRF tokens by manipulating GET requests. The root cause is inconsistent validation of CSRF tokens across HTTP methods, particularly on GET requests. In this case, the application incorrectly validated CSRF tokens for GET requests but did so correctly for POST requests. By modifying a legitimate request to use the GET method and moving parameters into the URL, the researcher discovered that the server did not validate the CSRF token. The attack involves creating an HTML PoC (proof-of-concept) with JavaScript to automatically submit the modified request, exploiting the victim without their interaction. This vulnerability emphasizes the importance of consistent validation for CSRF tokens across all HTTP methods. Key lesson: Validate CSRF tokens consistently regardless of HTTP method to maintain security. #BugBounty #WebSecurity #CSRF #VulnerabilityResearch

    smartpicks4u.medium.com/day-5-

  7. Day 5 — CSRF Token Bypass using GET Request
    This article discusses a Cross-Site Request Forgery (CSRF) vulnerability where an attacker can bypass CSRF tokens by manipulating GET requests. The root cause is inconsistent validation of CSRF tokens across HTTP methods, particularly on GET requests. In this case, the application incorrectly validated CSRF tokens for GET requests but did so correctly for POST requests. By modifying a legitimate request to use the GET method and moving parameters into the URL, the researcher discovered that the server did not validate the CSRF token. The attack involves creating an HTML PoC (proof-of-concept) with JavaScript to automatically submit the modified request, exploiting the victim without their interaction. This vulnerability emphasizes the importance of consistent validation for CSRF tokens across all HTTP methods. Key lesson: Validate CSRF tokens consistently regardless of HTTP method to maintain security. #BugBounty #WebSecurity #CSRF #VulnerabilityResearch

    smartpicks4u.medium.com/day-5-

  8. Уязвимости в мессенджере MAX

    С момента запуска программы Bug Bounty в июле 2025 года в системе накопилось уже 454 отчёта, из которых признаны валидными 288. Это не просто «рабочий процесс», а показатель
    enep-home.ru/2026/04/13/%d1%83

    #BugBounty #IDOR #MAX #безопасность #мессенджер #уязвимость

  9. I don't know enough about security research. For a project like Node.js does stopping bug bounties drastically impact anything?

    On the face of it, no money means people may be less incentivised to help or report, which feels bad.

    But Node.js is a massive concern, so is there enough goodwill and surface area that people will help and report anyway? Simply because big orgs rely on it?

    nodejs.org/en/blog/announcemen

    #Node #NodeJS #Security #SecurityResearch #BugBounty

  10. Subdomain Takeover Vulnerabilities and Prevention

    In this article, I cover:
    * How subdomain takeover vulnerabilities occur
    * Real-world exploitation scenarios
    Reconnaissance and detection techniques
    * Practical prevention and DNS hygiene strategies

    denizhalil.com/2026/02/16/subd

    #CyberSecurity #SubdomainTakeover #DNS #AttackSurface #BugBounty #RedTeam #BlueTeam #InfoSec #CloudSecurity #WebSecurity #EthicalHacking

  11. Subdomain Takeover Vulnerabilities and Prevention

    In this article, I cover:
    * How subdomain takeover vulnerabilities occur
    * Real-world exploitation scenarios
    Reconnaissance and detection techniques
    * Practical prevention and DNS hygiene strategies

    denizhalil.com/2026/02/16/subd

    #CyberSecurity #SubdomainTakeover #DNS #AttackSurface #BugBounty #RedTeam #BlueTeam #InfoSec #CloudSecurity #WebSecurity #EthicalHacking

  12. Subdomain Takeover Vulnerabilities and Prevention

    In this article, I cover:
    * How subdomain takeover vulnerabilities occur
    * Real-world exploitation scenarios
    Reconnaissance and detection techniques
    * Practical prevention and DNS hygiene strategies

    denizhalil.com/2026/02/16/subd

    #CyberSecurity #SubdomainTakeover #DNS #AttackSurface #BugBounty #RedTeam #BlueTeam #InfoSec #CloudSecurity #WebSecurity #EthicalHacking

  13. How I Found a CSRF Vulnerability That Could Take Over Student Accounts on an Educational Platform
    This vulnerability was a Cross-Site Request Forgery (CSRF) attack, allowing malicious users to hijack student accounts on an educational platform by manipulating a sensitive account management action (changing passwords) through an unsuspecting victim's browser session. The application failed to verify that the origin of the request was the legitimate user, instead relying on session cookies for authentication without additional CSRF protection. By using a crafted payload within a link, the researcher exploited the flawed security mechanism by forcing the victim's browser to make a password change request on behalf of the attacker. The impact was significant as unauthorized individuals could gain access to sensitive student accounts. The researcher received $500 as part of the bug bounty program, and the platform responded by implementing CSRF tokens for account management actions to prevent future attacks. Key lesson: Always implement CSRF tokens to protect sensitive user actions. #BugBounty #Cybersecurity #WebSecurity #CSRF

    medium.com/@s3clipt0r/how-i-fo

  14. How I Found a CSRF Vulnerability That Could Take Over Student Accounts on an Educational Platform
    This vulnerability was a Cross-Site Request Forgery (CSRF) attack, allowing malicious users to hijack student accounts on an educational platform by manipulating a sensitive account management action (changing passwords) through an unsuspecting victim's browser session. The application failed to verify that the origin of the request was the legitimate user, instead relying on session cookies for authentication without additional CSRF protection. By using a crafted payload within a link, the researcher exploited the flawed security mechanism by forcing the victim's browser to make a password change request on behalf of the attacker. The impact was significant as unauthorized individuals could gain access to sensitive student accounts. The researcher received $500 as part of the bug bounty program, and the platform responded by implementing CSRF tokens for account management actions to prevent future attacks. Key lesson: Always implement CSRF tokens to protect sensitive user actions. #BugBounty #Cybersecurity #WebSecurity #CSRF

    medium.com/@s3clipt0r/how-i-fo

  15. How I Found a CSRF Vulnerability That Could Take Over Student Accounts on an Educational Platform
    This vulnerability was a Cross-Site Request Forgery (CSRF) attack, allowing malicious users to hijack student accounts on an educational platform by manipulating a sensitive account management action (changing passwords) through an unsuspecting victim's browser session. The application failed to verify that the origin of the request was the legitimate user, instead relying on session cookies for authentication without additional CSRF protection. By using a crafted payload within a link, the researcher exploited the flawed security mechanism by forcing the victim's browser to make a password change request on behalf of the attacker. The impact was significant as unauthorized individuals could gain access to sensitive student accounts. The researcher received $500 as part of the bug bounty program, and the platform responded by implementing CSRF tokens for account management actions to prevent future attacks. Key lesson: Always implement CSRF tokens to protect sensitive user actions. #BugBounty #Cybersecurity #WebSecurity #CSRF

    medium.com/@s3clipt0r/how-i-fo

  16. How I Found a CSRF Vulnerability That Could Take Over Student Accounts on an Educational Platform
    This vulnerability was a Cross-Site Request Forgery (CSRF) attack, allowing malicious users to hijack student accounts on an educational platform by manipulating a sensitive account management action (changing passwords) through an unsuspecting victim's browser session. The application failed to verify that the origin of the request was the legitimate user, instead relying on session cookies for authentication without additional CSRF protection. By using a crafted payload within a link, the researcher exploited the flawed security mechanism by forcing the victim's browser to make a password change request on behalf of the attacker. The impact was significant as unauthorized individuals could gain access to sensitive student accounts. The researcher received $500 as part of the bug bounty program, and the platform responded by implementing CSRF tokens for account management actions to prevent future attacks. Key lesson: Always implement CSRF tokens to protect sensitive user actions. #BugBounty #Cybersecurity #WebSecurity #CSRF

    medium.com/@s3clipt0r/how-i-fo

  17. How I Found a CSRF Vulnerability That Could Take Over Student Accounts on an Educational Platform
    This vulnerability was a Cross-Site Request Forgery (CSRF) attack, allowing malicious users to hijack student accounts on an educational platform by manipulating a sensitive account management action (changing passwords) through an unsuspecting victim's browser session. The application failed to verify that the origin of the request was the legitimate user, instead relying on session cookies for authentication without additional CSRF protection. By using a crafted payload within a link, the researcher exploited the flawed security mechanism by forcing the victim's browser to make a password change request on behalf of the attacker. The impact was significant as unauthorized individuals could gain access to sensitive student accounts. The researcher received $500 as part of the bug bounty program, and the platform responded by implementing CSRF tokens for account management actions to prevent future attacks. Key lesson: Always implement CSRF tokens to protect sensitive user actions. #BugBounty #Cybersecurity #WebSecurity #CSRF

    medium.com/@s3clipt0r/how-i-fo

  18. When Old Breaches Meet New Code: Why Historical Leaks Still Matter
    This vulnerability demonstrates the persistence of historical breaches in current systems due to a lack of code updates or inadequate data sanitization. In this instance, the application used email addresses from an old data breach in its password recovery feature, allowing attackers to obtain user credentials by matching leaked emails to hashed passwords in a rainbow table (a precomputed table of hashed passwords). The attacker was able to bypass rate-limiting and CAPTCHA protections by using a Python script to automate the process. The mechanism relied on a combination of brute force and dictionary attacks, taking advantage of weak password choices by some users. The impact was significant, as attackers could gain unauthorized access to user accounts. No bounty amount was disclosed, but the platform addressed the issue by implementing a more secure password recovery process that no longer relies on leaked email addresses. Key takeaway: Keep your code updated and data secure by regularly sanitizing and rotating credentials from historical breaches. #BugBounty #Cybersecurity #WebSecurity #PasswordRecovery #DataBreach

    infosecwriteups.com/when-old-b

  19. When Old Breaches Meet New Code: Why Historical Leaks Still Matter
    This vulnerability demonstrates the persistence of historical breaches in current systems due to a lack of code updates or inadequate data sanitization. In this instance, the application used email addresses from an old data breach in its password recovery feature, allowing attackers to obtain user credentials by matching leaked emails to hashed passwords in a rainbow table (a precomputed table of hashed passwords). The attacker was able to bypass rate-limiting and CAPTCHA protections by using a Python script to automate the process. The mechanism relied on a combination of brute force and dictionary attacks, taking advantage of weak password choices by some users. The impact was significant, as attackers could gain unauthorized access to user accounts. No bounty amount was disclosed, but the platform addressed the issue by implementing a more secure password recovery process that no longer relies on leaked email addresses. Key takeaway: Keep your code updated and data secure by regularly sanitizing and rotating credentials from historical breaches. #BugBounty #Cybersecurity #WebSecurity #PasswordRecovery #DataBreach

    infosecwriteups.com/when-old-b

  20. Sequence [TryHackMe] [Writeup]

    Room Info Name: Sequence Platform: TryHackMe Difficulty: Medium Link: https://tryhackme.com/room/sequence Description: Chain multiple vulnerabilities to take control of a system. Task 1: Challenge Robert made some last-minute updates to the review.thm website before heading off on vacation. He claims that the secret information of the financiers is fully protected. But are his defenses truly airtight? Your challenge is to exploit the vulnerabilities and gain complete control of the […]

    aredopseagle.wordpress.com/202

  21. 🔎 Cybersecurity Challenge #6 – Spot the Vulnerability

    This application fetches an image from a URL provided by the user. Sounds harmless, right? 👨‍💻

    But allowing servers to request external resources based on user input can sometimes open the door to dangerous attacks.

    Take a closer look at how the URL is validated and how the request is made.

    ⚠️ Is the validation strong enough?

    Question: What security vulnerability exists in this code?

    A) SQL Injection
    B) Server-Side Request Forgery (SSRF)
    C) External XML Entity (XXE)
    D) URL Redirection

    💬 Comment your answer and tell us which line reveals the vulnerability!

    In the next post, I’ll reveal the correct answer and explain how attackers could exploit it in real-world environments.

    #cybersecurity #infosec #ethicalhacking #websecurity #bugbounty #securecoding #CyberKid #securitychallenge #SSRF

  22. To search for Google API keys recursively in the current folder and its sub-folders with ripgrep:

    rg 'AIza[0-9A-Za-z\-_]{35}' -o

    Also shared on Shodan Snippets:

    snippets.shodan.io/c/FHw2r7wWI

    #Security #OneLiner #Google #GoogleAPIKeys #APIkeys #ripgrep #Regex #BugBounty #Snippet

  23. To search for Google API keys recursively in the current folder and its sub-folders with ripgrep:

    rg 'AIza[0-9A-Za-z\-_]{35}' -o

    Also shared on Shodan Snippets:

    snippets.shodan.io/c/FHw2r7wWI

    #Security #OneLiner #Google #GoogleAPIKeys #APIkeys #ripgrep #Regex #BugBounty #Snippet

  24. To search for Google API keys recursively in the current folder and its sub-folders with ripgrep:

    rg 'AIza[0-9A-Za-z\-_]{35}' -o

    Also shared on Shodan Snippets:

    snippets.shodan.io/c/FHw2r7wWI

    #Security #OneLiner #Google #GoogleAPIKeys #APIkeys #ripgrep #Regex #BugBounty #Snippet

  25. If Claude Can Find serious cybersecurity Bug, Who Collects the Bounty?

    Bug bounty programs vs. $20/month reasoning — when the brutal question becomes: why pay five-figure bounties if a Claude Code subscription already finds entire classes of bugs? #BugBounty #VulnerabilityResearch #OffSec #AppSec #Infosec #AI #LLM #SecurityResearch #CyberSecurity red.anthropic.com/2026/zero-da

  26. weil jeder mit nem claude abo denkt er sei jetzt plötzlich security researcher und die bug bounty programme diverser opensource projekte mit slop flutet, stellen jetzt cURL und log4j ihre ein!

    die welt ein bisschen unsicherer machen - dank KI! 😠
    #cURL #log4j #KI #BugBounty #CyberSecurity #foss #opensource

  27. 🔓 Found critical vulns in Taimi (LGBTQ+ dating app) - all fixed, $10k bounty

    What I found:

    • "Expiring" videos didn't expire, URLs stayed valid forever
    • Decrement attachment ID = anyone's private videos
    • Location feature bypassed photo permission checks (why upload a map preview image through the photo system??)
    • Fake system messages (made a Raid Shadow Legends sponsorship lol)

    The good news: Taimi actually handled this right. Fast response, $10k bounty, everything fixed quickly. No lawyers, no threats.

    This is how disclosure should work. Take notes, Lovense.

    Full writeup: bobdahacker.com/blog/taimi-idor

    #InfoSec #BugBounty #ResponsibleDisclosure #IDOR #Taimi #DatingApp #Security #Privacy #CyberSecurity #LGBTQ

  28. Хватит страдать в токсичных отношениях с Burp Suite. Пора быть счастливым с Caido

    Burp Suite убедил вас, что настоящий инструмент должен быть тяжёлым, капризным и заставлять подстраиваться под себя. Caido доказал обратное: тот же уровень функциональности, но без боли, без ожидания и без лишних гигабайт. Всё просто работает - быстро, стабильно и без нервов. Страдать было необязательно. Пора наконец выдохнуть и работать с удовольствием. Узнать, как жить счастливо без Burp Suite

    habr.com/ru/articles/967644/

    #Caido #багхантинг #bugbounty #burp #slonser

  29. Apple podwaja nagrodę w programie Bug Bounty do 2 mln USD za ataki na poziomie szpiegowskim

    Apple ogłosiło nową, ulepszoną wersję swojego programu Bug Bounty, w którym nagroda za łańcuchy exploitów porównywalne do ataków szpiegowskich wzrosła do 2 mln USD.

    Łączne wypłaty z bonusami za obejście Lockdown Mode i luki w wersjach beta mogą przekroczyć 5 mln USD, co Apple nazywa największą nagrodą oferowaną przez jakikolwiek program bug bounty.

    Nowy program skupia się na kompletnych łańcuchach exploitów, a nie pojedynczych lukach, co odzwierciedla realne ataki. Nagrody za zdalne wektory ataku znacząco wzrosły, podczas gdy mniej powszechne kategorie otrzymają mniejsze wypłaty.

    Apple wprowadza też „Target Flags”, inspirowane grami typu capture-the-flag. Pozwalają one badaczom udowodnić poziom uzyskanego dostępu (np. wykonanie kodu lub arbitralny odczyt/zapis). Po weryfikacji przez Apple nagroda jest wypłacana w najbliższym cyklu płatności, bez oczekiwania na poprawkę systemu.

    Nowe kategorie obejmują m.in.:

    • One-click WebKit sandbox escapes – do 300 000 USD
    • Exploity bezprzewodowe – do 1 mln USD
    • Pełne obejście Gatekeeper w macOS – 100 000 USD

    Program wchodzi w życie od listopada 2025, a od startu w 2020 Apple wypłaciło ponad 35 mln USD ponad 800 badaczom.

    Podobne programy mają inne filmy technologiczne z całego świata, w tym Synology, o czym szerzej posłuchasz w jednym z odcinków mojego podcastu „Bo czemu nie?”.

    #Apple #AppleSecurity #Bezpieczeństwo #bezpieczeństwosystemów #BugBounty #cybersecurity #exploit #exploitchains #hackowanie #iOS #LockdownMode #macOS #nagroda #programiści #technews #vulnerability

  30. RippleX Taps Immunefi for $200K XRPL Attackathon to Strengthen DeFi Security - TLDR:

    RippleX and Immunefi have launched a $200K Attackathon to test the XRPL Lending Pr... - blockonomi.com/ripplex-taps-im #blockchainsecurity #attackathon #bugbounty #xrpledger #security #immunefi #ripplex #defi #xrpl