home.social

#dataexposure — Public Fediverse posts

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

fetched live
  1. 🍝 New Blog Post: tl;dv (Too Lazy; Didn't Validate): 181,874 Meetings Left Wide Open

    tl;dv's Firestore database has zero tenant isolation on their meetings collection. Any free-tier user can query every meeting on the platform. 181,874 meetings. 84,312 users. 35,003 domains.

    What's exposed:

    • Creator emails, conference IDs, recording status, timestamps
    • Live calls you can join uninvited (I joined 2, including one with the Malaysian Ministry of Education)
    • Government meetings from 23 countries
    • Corporate meetings from thousands of companies

    Reported January 28th. Six months later, still not fixed. CTO never responded. Their Firestore database has better uptime than their inbox.

    Full writeup: bobdahacker.com/blog/tldv-hack

    #InfoSec #BugBounty #ResponsibleDisclosure #Firebase #Security #CyberSecurity #Privacy #DataExposure #APISecurity #tldv #MeetingPrivacy

  2. 🍝 New Blog Post: tl;dv (Too Lazy; Didn't Validate): 181,874 Meetings Left Wide Open

    tl;dv's Firestore database has zero tenant isolation on their meetings collection. Any free-tier user can query every meeting on the platform. 181,874 meetings. 84,312 users. 35,003 domains.

    What's exposed:

    • Creator emails, conference IDs, recording status, timestamps
    • Live calls you can join uninvited (I joined 2, including one with the Malaysian Ministry of Education)
    • Government meetings from 23 countries
    • Corporate meetings from thousands of companies

    Reported January 28th. Six months later, still not fixed. CTO never responded. Their Firestore database has better uptime than their inbox.

    Full writeup: bobdahacker.com/blog/tldv-hack

    #InfoSec #BugBounty #ResponsibleDisclosure #Firebase #Security #CyberSecurity #Privacy #DataExposure #APISecurity #tldv #MeetingPrivacy

  3. 🍝 New Blog Post: tl;dv (Too Lazy; Didn't Validate): 181,874 Meetings Left Wide Open

    tl;dv's Firestore database has zero tenant isolation on their meetings collection. Any free-tier user can query every meeting on the platform. 181,874 meetings. 84,312 users. 35,003 domains.

    What's exposed:

    • Creator emails, conference IDs, recording status, timestamps
    • Live calls you can join uninvited (I joined 2, including one with the Malaysian Ministry of Education)
    • Government meetings from 23 countries
    • Corporate meetings from thousands of companies

    Reported January 28th. Six months later, still not fixed. CTO never responded. Their Firestore database has better uptime than their inbox.

    Full writeup: bobdahacker.com/blog/tldv-hack

    #InfoSec #BugBounty #ResponsibleDisclosure #Firebase #Security #CyberSecurity #Privacy #DataExposure #APISecurity #tldv #MeetingPrivacy

  4. 🍝 New Blog Post: tl;dv (Too Lazy; Didn't Validate): 181,874 Meetings Left Wide Open

    tl;dv's Firestore database has zero tenant isolation on their meetings collection. Any free-tier user can query every meeting on the platform. 181,874 meetings. 84,312 users. 35,003 domains.

    What's exposed:

    • Creator emails, conference IDs, recording status, timestamps
    • Live calls you can join uninvited (I joined 2, including one with the Malaysian Ministry of Education)
    • Government meetings from 23 countries
    • Corporate meetings from thousands of companies

    Reported January 28th. Six months later, still not fixed. CTO never responded. Their Firestore database has better uptime than their inbox.

    Full writeup: bobdahacker.com/blog/tldv-hack

    #InfoSec #BugBounty #ResponsibleDisclosure #Firebase #Security #CyberSecurity #Privacy #DataExposure #APISecurity #tldv #MeetingPrivacy

  5. 🍝 New Blog Post: tl;dv (Too Lazy; Didn't Validate): 181,874 Meetings Left Wide Open

    tl;dv's Firestore database has zero tenant isolation on their meetings collection. Any free-tier user can query every meeting on the platform. 181,874 meetings. 84,312 users. 35,003 domains.

    What's exposed:

    • Creator emails, conference IDs, recording status, timestamps
    • Live calls you can join uninvited (I joined 2, including one with the Malaysian Ministry of Education)
    • Government meetings from 23 countries
    • Corporate meetings from thousands of companies

    Reported January 28th. Six months later, still not fixed. CTO never responded. Their Firestore database has better uptime than their inbox.

    Full writeup: bobdahacker.com/blog/tldv-hack

    #InfoSec #BugBounty #ResponsibleDisclosure #Firebase #Security #CyberSecurity #Privacy #DataExposure #APISecurity #tldv #MeetingPrivacy

  6. 🙏 New Blog Post

    The Pope's official prayer app has an IDOR that lets anyone pull user data for all 719,517 accounts. One GET request per user. No auth check.

    What's exposed:

    • Email addresses
    • Names
    • Country
    • Date of birth (they call it "borned_date" lol)
    • Account role (it's "PRAYER" for everyone, obviously)

    Also found:

    • Signup endpoint returns the email verification token in the response body, so you can verify accounts without accessing the inbox
    • Their verification emails fail their own domain's authentication requirements

    Reported January 3rd. Emailed 9 people. A journalist also contacted them. Zero responses. Still live six months later. Vow of silence I guess.

    Full writeup: bobdahacker.com/blog/click-to-

    #InfoSec #BugBounty #ResponsibleDisclosure #IDOR #Security #CyberSecurity #Privacy #DataExposure #ClickToPray #Vatican #APISecurity

  7. 🙏 New Blog Post

    The Pope's official prayer app has an IDOR that lets anyone pull user data for all 719,517 accounts. One GET request per user. No auth check.

    What's exposed:

    • Email addresses
    • Names
    • Country
    • Date of birth (they call it "borned_date" lol)
    • Account role (it's "PRAYER" for everyone, obviously)

    Also found:

    • Signup endpoint returns the email verification token in the response body, so you can verify accounts without accessing the inbox
    • Their verification emails fail their own domain's authentication requirements

    Reported January 3rd. Emailed 9 people. A journalist also contacted them. Zero responses. Still live six months later. Vow of silence I guess.

    Full writeup: bobdahacker.com/blog/click-to-

    #InfoSec #BugBounty #ResponsibleDisclosure #IDOR #Security #CyberSecurity #Privacy #DataExposure #ClickToPray #Vatican #APISecurity

  8. 🙏 New Blog Post

    The Pope's official prayer app has an IDOR that lets anyone pull user data for all 719,517 accounts. One GET request per user. No auth check.

    What's exposed:

    • Email addresses
    • Names
    • Country
    • Date of birth (they call it "borned_date" lol)
    • Account role (it's "PRAYER" for everyone, obviously)

    Also found:

    • Signup endpoint returns the email verification token in the response body, so you can verify accounts without accessing the inbox
    • Their verification emails fail their own domain's authentication requirements

    Reported January 3rd. Emailed 9 people. A journalist also contacted them. Zero responses. Still live six months later. Vow of silence I guess.

    Full writeup: bobdahacker.com/blog/click-to-

    #InfoSec #BugBounty #ResponsibleDisclosure #IDOR #Security #CyberSecurity #Privacy #DataExposure #ClickToPray #Vatican #APISecurity

  9. 🙏 New Blog Post

    The Pope's official prayer app has an IDOR that lets anyone pull user data for all 719,517 accounts. One GET request per user. No auth check.

    What's exposed:

    • Email addresses
    • Names
    • Country
    • Date of birth (they call it "borned_date" lol)
    • Account role (it's "PRAYER" for everyone, obviously)

    Also found:

    • Signup endpoint returns the email verification token in the response body, so you can verify accounts without accessing the inbox
    • Their verification emails fail their own domain's authentication requirements

    Reported January 3rd. Emailed 9 people. A journalist also contacted them. Zero responses. Still live six months later. Vow of silence I guess.

    Full writeup: bobdahacker.com/blog/click-to-

    #InfoSec #BugBounty #ResponsibleDisclosure #IDOR #Security #CyberSecurity #Privacy #DataExposure #ClickToPray #Vatican #APISecurity

  10. 🙏 New Blog Post

    The Pope's official prayer app has an IDOR that lets anyone pull user data for all 719,517 accounts. One GET request per user. No auth check.

    What's exposed:

    • Email addresses
    • Names
    • Country
    • Date of birth (they call it "borned_date" lol)
    • Account role (it's "PRAYER" for everyone, obviously)

    Also found:

    • Signup endpoint returns the email verification token in the response body, so you can verify accounts without accessing the inbox
    • Their verification emails fail their own domain's authentication requirements

    Reported January 3rd. Emailed 9 people. A journalist also contacted them. Zero responses. Still live six months later. Vow of silence I guess.

    Full writeup: bobdahacker.com/blog/click-to-

    #InfoSec #BugBounty #ResponsibleDisclosure #IDOR #Security #CyberSecurity #Privacy #DataExposure #ClickToPray #Vatican #APISecurity

  11. LAPD lets contract with surveillance giant Flock expire, citing ‘serious concerns’ over civil liberties and privacy

    The Los Angeles Police Department (LAPD) is reportedly ending its deal with Flock Safety, a surveillance company that…
    #NewsBeep #News #Headlines #cybersecurity #dataexposure #Flock #LAPD #Privacy #surveillance #UnitedStates #Us #USA
    newsbeep.com/642022/

  12. 🟡 Cyber Incident | 7/10
    🇺🇸

    Data exposure at Peter Thiel-linked Dialog network
    A misconfigured website exposed personal details and login tokens of 222 registrants, including a senior White House intelligence official and an active-duty Tier 1 intelligence officer. The Pentagon is investigating the breach.

    #OSINT #NewsGroup #CyberIncident #DataExposure #Pentagon #US

  13. 🟡 Cyber Incident | 7/10
    🇺🇸

    Data exposure at Peter Thiel-linked Dialog network
    A misconfigured website exposed personal details and login tokens of 222 registrants, including a senior White House intelligence official and an active-duty Tier 1 intelligence officer. The Pentagon is investigating the breach.

    #OSINT #NewsGroup #CyberIncident #DataExposure #Pentagon #US

  14. 🟡 Cyber Incident | 7/10
    🇺🇸

    Data exposure at Peter Thiel-linked Dialog network
    A misconfigured website exposed personal details and login tokens of 222 registrants, including a senior White House intelligence official and an active-duty Tier 1 intelligence officer. The Pentagon is investigating the breach.

    #OSINT #NewsGroup #CyberIncident #DataExposure #Pentagon #US

  15. 🟡 Cyber Incident | 7/10
    🇺🇸

    Data exposure at Peter Thiel-linked Dialog network
    A misconfigured website exposed personal details and login tokens of 222 registrants, including a senior White House intelligence official and an active-duty Tier 1 intelligence officer. The Pentagon is investigating the breach.

    #OSINT #NewsGroup #CyberIncident #DataExposure #Pentagon #US

  16. ✈️ New Blog Post: Your Boarding Pass Is a Skeleton Key. Frontier Airlines Doesn't Care.

    Frontier's mobile API returns full passport numbers, home addresses, children's DOB, credit card details, and KTNs for any booking. The only auth? A PNR and last name. Printed on every boarding pass.

    Reported March 3rd. 105 days later, still live. They fixed the least important vuln and ghosted me on the rest. They also updated the website code and somehow made the leaks worse.

    Full writeup: bobdahacker.com/blog/frontier-

    #InfoSec #BugBounty #ResponsibleDisclosure #FrontierAirlines #Security #CyberSecurity #Privacy #Aviation #PCIDSS #DataExposure

  17. ✈️ New Blog Post: Your Boarding Pass Is a Skeleton Key. Frontier Airlines Doesn't Care.

    Frontier's mobile API returns full passport numbers, home addresses, children's DOB, credit card details, and KTNs for any booking. The only auth? A PNR and last name. Printed on every boarding pass.

    Reported March 3rd. 105 days later, still live. They fixed the least important vuln and ghosted me on the rest. They also updated the website code and somehow made the leaks worse.

    Full writeup: bobdahacker.com/blog/frontier-

    #InfoSec #BugBounty #ResponsibleDisclosure #FrontierAirlines #Security #CyberSecurity #Privacy #Aviation #PCIDSS #DataExposure

  18. ✈️ New Blog Post: Your Boarding Pass Is a Skeleton Key. Frontier Airlines Doesn't Care.

    Frontier's mobile API returns full passport numbers, home addresses, children's DOB, credit card details, and KTNs for any booking. The only auth? A PNR and last name. Printed on every boarding pass.

    Reported March 3rd. 105 days later, still live. They fixed the least important vuln and ghosted me on the rest. They also updated the website code and somehow made the leaks worse.

    Full writeup: bobdahacker.com/blog/frontier-

    #InfoSec #BugBounty #ResponsibleDisclosure #FrontierAirlines #Security #CyberSecurity #Privacy #Aviation #PCIDSS #DataExposure

  19. ✈️ New Blog Post: Your Boarding Pass Is a Skeleton Key. Frontier Airlines Doesn't Care.

    Frontier's mobile API returns full passport numbers, home addresses, children's DOB, credit card details, and KTNs for any booking. The only auth? A PNR and last name. Printed on every boarding pass.

    Reported March 3rd. 105 days later, still live. They fixed the least important vuln and ghosted me on the rest. They also updated the website code and somehow made the leaks worse.

    Full writeup: bobdahacker.com/blog/frontier-

    #InfoSec #BugBounty #ResponsibleDisclosure #FrontierAirlines #Security #CyberSecurity #Privacy #Aviation #PCIDSS #DataExposure

  20. ✈️ New Blog Post: Your Boarding Pass Is a Skeleton Key. Frontier Airlines Doesn't Care.

    Frontier's mobile API returns full passport numbers, home addresses, children's DOB, credit card details, and KTNs for any booking. The only auth? A PNR and last name. Printed on every boarding pass.

    Reported March 3rd. 105 days later, still live. They fixed the least important vuln and ghosted me on the rest. They also updated the website code and somehow made the leaks worse.

    Full writeup: bobdahacker.com/blog/frontier-

    #InfoSec #BugBounty #ResponsibleDisclosure #FrontierAirlines #Security #CyberSecurity #Privacy #Aviation #PCIDSS #DataExposure

  21. CEO's File Share Mishap Exposes Workplace Security Lapses

    Imagine being called in to help a CEO recover deleted files, only to discover a shocking secret: a treasure trove of explicit content stored on a company file share that's accessible to anyone. The awkward moment that followed will leave you cringing - and wondering how something so sensitive could be so carelessly exposed.

    osintsights.com/ceos-file-shar

    #DataExposure #WorkplaceSecurity #FileShare #InsiderThreats #Ceo

  22. Trump Mobile Website Exposed Thousands of User Records

    A shocking security lapse has been uncovered on the Trump Mobile website, allegedly exposing thousands of users' sensitive information, according to a report by The Register. The breach claim, made by a techie, raises serious concerns about the website's data protection measures.

    osintsights.com/trump-mobile-w

    #DataExposure #TrumpMobile #EmergingThreats #UserDataLeak #WebsiteSecurity

  23. UK Water Supplier Fined $1.3M for Data Exposure Lapse

    A UK water supplier has been slapped with a $1.3 million fine after a devastating cyber attack exposed the personal data of nearly 664,000 customers and employees, with sensitive information even being published on the dark web. The hefty penalty was reduced by 40% after the company admitted liability and cooperated with investigators.

    osintsights.com/uk-water-suppl

    #DataExposure #Uk #WaterSector #EmergingThreats #InformationCommissionersOffice

  24. Defense Contractor Exposes Military Training Data Through API Flaw

    A defense contractor's careless API flaw left sensitive military training data vulnerable, sparking a 152-day saga between the contractor and the open-source security project Strix that ultimately led to the exposure being patched. The breach was caused by a low-privilege account having broad access to user records and…

    osintsights.com/defense-contra

    #ApiSecurity #MilitaryTraining #DefenseContractor #DataExposure #EmergingThreats

  25. Voter Data Exposes Personal Info to Potential Abuse

    Your voter data is at risk of being exposed and used against you, with publicly available registration files potentially revealing sensitive information about you and your family. Even redacted files can be easily linked to other public datasets, making it simple for employers, fraud rings, or others to access your personal info.

    osintsights.com/voter-data-exp

    #VoterDataSecurity #DataExposure #IdentityDisclosure #PublicRecords #Reidentification

  26. AI Agents Fuel Cybersecurity Breaches at Most Firms

    As AI agents increasingly power business operations, they're also fueling cybersecurity breaches at most firms, leading to data exposure, operational disruption, and financial losses. The rapid rise of AI is sparking a pressing dilemma: how can organizations balance innovation with control?

    osintsights.com/ai-agents-fuel

    #CloudSecurity #AiAgents #CybersecurityBreaches #DataExposure #OperationalDisruption

  27. Incident summary:
    Target: PayPal - Working Capital (PPWC) loan app
    Root cause: Software code error
    Exposure window: July 1- Dec 13, 2025
    Discovery: Dec 12, 2025
    Scope: ~100 users

    Data exposed:
    • SSN
    • DOB
    • Contact & business details

    No core system compromise reported.
    Unauthorized transactions observed in limited cases.

    Credit monitoring via Equifax provided.
    Key considerations:

    – Secure SDLC gaps?
    – Change management review failure?
    – Logging & anomaly detection delay?
    – Exposure vs intrusion classification challenges

    Six months of unnoticed PII exposure highlights how application-layer misconfigurations can rival full breaches in impact.

    How would you design detection controls to catch this earlier?

    Engage below.
    Follow @technadu for technical cybersecurity coverage.

    Source: bleepingcomputer.com/news/secu

    #ThreatAnalysis #SecureSDLC #FintechSecurity #ApplicationSecurity #DataExposure #CyberRisk #DFIR #Governance #Infosec

  28. Incident summary:
    Target: PayPal - Working Capital (PPWC) loan app
    Root cause: Software code error
    Exposure window: July 1- Dec 13, 2025
    Discovery: Dec 12, 2025
    Scope: ~100 users

    Data exposed:
    • SSN
    • DOB
    • Contact & business details

    No core system compromise reported.
    Unauthorized transactions observed in limited cases.

    Credit monitoring via Equifax provided.
    Key considerations:

    – Secure SDLC gaps?
    – Change management review failure?
    – Logging & anomaly detection delay?
    – Exposure vs intrusion classification challenges

    Six months of unnoticed PII exposure highlights how application-layer misconfigurations can rival full breaches in impact.

    How would you design detection controls to catch this earlier?

    Engage below.
    Follow @technadu for technical cybersecurity coverage.

    Source: bleepingcomputer.com/news/secu

    #ThreatAnalysis #SecureSDLC #FintechSecurity #ApplicationSecurity #DataExposure #CyberRisk #DFIR #Governance #Infosec

  29. Incident summary:
    Target: PayPal - Working Capital (PPWC) loan app
    Root cause: Software code error
    Exposure window: July 1- Dec 13, 2025
    Discovery: Dec 12, 2025
    Scope: ~100 users

    Data exposed:
    • SSN
    • DOB
    • Contact & business details

    No core system compromise reported.
    Unauthorized transactions observed in limited cases.

    Credit monitoring via Equifax provided.
    Key considerations:

    – Secure SDLC gaps?
    – Change management review failure?
    – Logging & anomaly detection delay?
    – Exposure vs intrusion classification challenges

    Six months of unnoticed PII exposure highlights how application-layer misconfigurations can rival full breaches in impact.

    How would you design detection controls to catch this earlier?

    Engage below.
    Follow @technadu for technical cybersecurity coverage.

    Source: bleepingcomputer.com/news/secu

    #ThreatAnalysis #SecureSDLC #FintechSecurity #ApplicationSecurity #DataExposure #CyberRisk #DFIR #Governance #Infosec

  30. Incident summary:
    Target: PayPal - Working Capital (PPWC) loan app
    Root cause: Software code error
    Exposure window: July 1- Dec 13, 2025
    Discovery: Dec 12, 2025
    Scope: ~100 users

    Data exposed:
    • SSN
    • DOB
    • Contact & business details

    No core system compromise reported.
    Unauthorized transactions observed in limited cases.

    Credit monitoring via Equifax provided.
    Key considerations:

    – Secure SDLC gaps?
    – Change management review failure?
    – Logging & anomaly detection delay?
    – Exposure vs intrusion classification challenges

    Six months of unnoticed PII exposure highlights how application-layer misconfigurations can rival full breaches in impact.

    How would you design detection controls to catch this earlier?

    Engage below.
    Follow @technadu for technical cybersecurity coverage.

    Source: bleepingcomputer.com/news/secu

    #ThreatAnalysis #SecureSDLC #FintechSecurity #ApplicationSecurity #DataExposure #CyberRisk #DFIR #Governance #Infosec

  31. ShinyHunters has listed a 1.67 GB JSON dataset allegedly containing 600K+ customer records tied to Canada Goose.
    Reported by BleepingComputer.

    Dataset reportedly includes:
    • checkout_id, cart_token schema indicators
    • Shipping lines & order values
    • IP telemetry
    • Device/browser metadata
    • Partial PAN (BIN + last four)
    • Authorization metadata
    No full card numbers observed in samples.

    Canada Goose states no evidence of breach of its own systems; attackers claim third-party processor origin.
    Security implications:
    • BIN + last four enable targeted card fraud attempts
    • Order value profiling identifies high-value targets
    • IP/device metadata aids social engineering
    • Historical datasets still carry active fraud potential
    Is vendor risk management keeping pace with SaaS-based commerce stacks?

    Source: bleepingcomputer.com/news/secu

    Engage below.
    Follow @technadu for advanced threat analysis.

    #ThreatIntel #DataLeak #VendorRisk #RetailSecurity #FraudPrevention #Infosec #CloudSecurity #DataExposure #ShinyHunters #CyberDefense #PrivacyEngineering

  32. ShinyHunters has listed a 1.67 GB JSON dataset allegedly containing 600K+ customer records tied to Canada Goose.
    Reported by BleepingComputer.

    Dataset reportedly includes:
    • checkout_id, cart_token schema indicators
    • Shipping lines & order values
    • IP telemetry
    • Device/browser metadata
    • Partial PAN (BIN + last four)
    • Authorization metadata
    No full card numbers observed in samples.

    Canada Goose states no evidence of breach of its own systems; attackers claim third-party processor origin.
    Security implications:
    • BIN + last four enable targeted card fraud attempts
    • Order value profiling identifies high-value targets
    • IP/device metadata aids social engineering
    • Historical datasets still carry active fraud potential
    Is vendor risk management keeping pace with SaaS-based commerce stacks?

    Source: bleepingcomputer.com/news/secu

    Engage below.
    Follow @technadu for advanced threat analysis.

    #ThreatIntel #DataLeak #VendorRisk #RetailSecurity #FraudPrevention #Infosec #CloudSecurity #DataExposure #ShinyHunters #CyberDefense #PrivacyEngineering

  33. ShinyHunters has listed a 1.67 GB JSON dataset allegedly containing 600K+ customer records tied to Canada Goose.
    Reported by BleepingComputer.

    Dataset reportedly includes:
    • checkout_id, cart_token schema indicators
    • Shipping lines & order values
    • IP telemetry
    • Device/browser metadata
    • Partial PAN (BIN + last four)
    • Authorization metadata
    No full card numbers observed in samples.

    Canada Goose states no evidence of breach of its own systems; attackers claim third-party processor origin.
    Security implications:
    • BIN + last four enable targeted card fraud attempts
    • Order value profiling identifies high-value targets
    • IP/device metadata aids social engineering
    • Historical datasets still carry active fraud potential
    Is vendor risk management keeping pace with SaaS-based commerce stacks?

    Source: bleepingcomputer.com/news/secu

    Engage below.
    Follow @technadu for advanced threat analysis.

    #ThreatIntel #DataLeak #VendorRisk #RetailSecurity #FraudPrevention #Infosec #CloudSecurity #DataExposure #ShinyHunters #CyberDefense #PrivacyEngineering

  34. ShinyHunters has listed a 1.67 GB JSON dataset allegedly containing 600K+ customer records tied to Canada Goose.
    Reported by BleepingComputer.

    Dataset reportedly includes:
    • checkout_id, cart_token schema indicators
    • Shipping lines & order values
    • IP telemetry
    • Device/browser metadata
    • Partial PAN (BIN + last four)
    • Authorization metadata
    No full card numbers observed in samples.

    Canada Goose states no evidence of breach of its own systems; attackers claim third-party processor origin.
    Security implications:
    • BIN + last four enable targeted card fraud attempts
    • Order value profiling identifies high-value targets
    • IP/device metadata aids social engineering
    • Historical datasets still carry active fraud potential
    Is vendor risk management keeping pace with SaaS-based commerce stacks?

    Source: bleepingcomputer.com/news/secu

    Engage below.
    Follow @technadu for advanced threat analysis.

    #ThreatIntel #DataLeak #VendorRisk #RetailSecurity #FraudPrevention #Infosec #CloudSecurity #DataExposure #ShinyHunters #CyberDefense #PrivacyEngineering

  35. Substack has disclosed a security incident involving unauthorized access to limited user data, reportedly obtained through scraping activity described by the threat actor as “noisy.”

    The company states that credentials and financial information were not affected, and that mitigations were implemented quickly after discovery. Users have been advised to remain cautious of potential phishing attempts.

    From an infosec perspective, this incident underscores challenges around detection timing, data exposure via scraping, and post-incident communication.

    How should platforms better monitor and respond to large-scale scraping risks?

    Source: securityweek.com/substack-disc

    Engage in the discussion and follow @technadu for measured cybersecurity analysis.

    #Infosec #DataExposure #Scraping #IncidentResponse #CyberRisk #TechNadu #SecurityOperations

  36. Substack has disclosed a security incident involving unauthorized access to limited user data, reportedly obtained through scraping activity described by the threat actor as “noisy.”

    The company states that credentials and financial information were not affected, and that mitigations were implemented quickly after discovery. Users have been advised to remain cautious of potential phishing attempts.

    From an infosec perspective, this incident underscores challenges around detection timing, data exposure via scraping, and post-incident communication.

    How should platforms better monitor and respond to large-scale scraping risks?

    Source: securityweek.com/substack-disc

    Engage in the discussion and follow @technadu for measured cybersecurity analysis.

    #Infosec #DataExposure #Scraping #IncidentResponse #CyberRisk #TechNadu #SecurityOperations

  37. Substack has disclosed a security incident involving unauthorized access to limited user data, reportedly obtained through scraping activity described by the threat actor as “noisy.”

    The company states that credentials and financial information were not affected, and that mitigations were implemented quickly after discovery. Users have been advised to remain cautious of potential phishing attempts.

    From an infosec perspective, this incident underscores challenges around detection timing, data exposure via scraping, and post-incident communication.

    How should platforms better monitor and respond to large-scale scraping risks?

    Source: securityweek.com/substack-disc

    Engage in the discussion and follow @technadu for measured cybersecurity analysis.

    #Infosec #DataExposure #Scraping #IncidentResponse #CyberRisk #TechNadu #SecurityOperations

  38. Substack has disclosed a security incident involving unauthorized access to limited user data, reportedly obtained through scraping activity described by the threat actor as “noisy.”

    The company states that credentials and financial information were not affected, and that mitigations were implemented quickly after discovery. Users have been advised to remain cautious of potential phishing attempts.

    From an infosec perspective, this incident underscores challenges around detection timing, data exposure via scraping, and post-incident communication.

    How should platforms better monitor and respond to large-scale scraping risks?

    Source: securityweek.com/substack-disc

    Engage in the discussion and follow @technadu for measured cybersecurity analysis.

    #Infosec #DataExposure #Scraping #IncidentResponse #CyberRisk #TechNadu #SecurityOperations

  39. SoundCloud’s December 2025 breach has been added to HIBP, confirming exposure of ~29.8M user accounts.

    The incident stemmed from unauthorized access to an internal service dashboard that enabled correlation of email addresses with public profile data. No credentials or financial information were compromised, but the case highlights how internal tooling can expand the attack surface.

    What practical controls help reduce correlation risk in large platforms?
    Source: cyberinsider.com/soundcloud-br

    Share insights and follow TechNadu for independent InfoSec coverage.

    #InfoSec #SoundCloud #HIBP #DataExposure #PrivacyEngineering #CyberRisk #SecurityOperations

  40. SoundCloud’s December 2025 breach has been added to HIBP, confirming exposure of ~29.8M user accounts.

    The incident stemmed from unauthorized access to an internal service dashboard that enabled correlation of email addresses with public profile data. No credentials or financial information were compromised, but the case highlights how internal tooling can expand the attack surface.

    What practical controls help reduce correlation risk in large platforms?
    Source: cyberinsider.com/soundcloud-br

    Share insights and follow TechNadu for independent InfoSec coverage.

    #InfoSec #SoundCloud #HIBP #DataExposure #PrivacyEngineering #CyberRisk #SecurityOperations

  41. SoundCloud’s December 2025 breach has been added to HIBP, confirming exposure of ~29.8M user accounts.

    The incident stemmed from unauthorized access to an internal service dashboard that enabled correlation of email addresses with public profile data. No credentials or financial information were compromised, but the case highlights how internal tooling can expand the attack surface.

    What practical controls help reduce correlation risk in large platforms?
    Source: cyberinsider.com/soundcloud-br

    Share insights and follow TechNadu for independent InfoSec coverage.

    #InfoSec #SoundCloud #HIBP #DataExposure #PrivacyEngineering #CyberRisk #SecurityOperations

  42. SoundCloud’s December 2025 breach has been added to HIBP, confirming exposure of ~29.8M user accounts.

    The incident stemmed from unauthorized access to an internal service dashboard that enabled correlation of email addresses with public profile data. No credentials or financial information were compromised, but the case highlights how internal tooling can expand the attack surface.

    What practical controls help reduce correlation risk in large platforms?
    Source: cyberinsider.com/soundcloud-br

    Share insights and follow TechNadu for independent InfoSec coverage.

    #InfoSec #SoundCloud #HIBP #DataExposure #PrivacyEngineering #CyberRisk #SecurityOperations

  43. The reported BreachForums database exposure illustrates a recurring pattern in underground ecosystems: infrastructure weaknesses outweigh perceived anonymity.

    Key considerations:
    • Metadata remains a critical risk vector
    • Forum resilience often masks fragile backends
    • Legal and reputational fallout can be long-lasting

    This incident reinforces why data minimization and secure configuration matter - regardless of intent or audience.

    Source: cybersecuritynews.com/breachfo

    Join the discussion and follow @technadu for fact-based cybersecurity reporting.

    #InfoSec #ThreatIntel #DarkWeb #DataExposure #CyberRisk #OperationalSecurity

  44. The reported BreachForums database exposure illustrates a recurring pattern in underground ecosystems: infrastructure weaknesses outweigh perceived anonymity.

    Key considerations:
    • Metadata remains a critical risk vector
    • Forum resilience often masks fragile backends
    • Legal and reputational fallout can be long-lasting

    This incident reinforces why data minimization and secure configuration matter - regardless of intent or audience.

    Source: cybersecuritynews.com/breachfo

    Join the discussion and follow @technadu for fact-based cybersecurity reporting.

    #InfoSec #ThreatIntel #DarkWeb #DataExposure #CyberRisk #OperationalSecurity

  45. The reported BreachForums database exposure illustrates a recurring pattern in underground ecosystems: infrastructure weaknesses outweigh perceived anonymity.

    Key considerations:
    • Metadata remains a critical risk vector
    • Forum resilience often masks fragile backends
    • Legal and reputational fallout can be long-lasting

    This incident reinforces why data minimization and secure configuration matter - regardless of intent or audience.

    Source: cybersecuritynews.com/breachfo

    Join the discussion and follow @technadu for fact-based cybersecurity reporting.

    #InfoSec #ThreatIntel #DarkWeb #DataExposure #CyberRisk #OperationalSecurity

  46. The reported BreachForums database exposure illustrates a recurring pattern in underground ecosystems: infrastructure weaknesses outweigh perceived anonymity.

    Key considerations:
    • Metadata remains a critical risk vector
    • Forum resilience often masks fragile backends
    • Legal and reputational fallout can be long-lasting

    This incident reinforces why data minimization and secure configuration matter - regardless of intent or audience.

    Source: cybersecuritynews.com/breachfo

    Join the discussion and follow @technadu for fact-based cybersecurity reporting.

    #InfoSec #ThreatIntel #DarkWeb #DataExposure #CyberRisk #OperationalSecurity

  47. Researchers enumerated 3.5B WhatsApp phone numbers through the platform’s contact-discovery feature, revealing public profile photos and text for millions of users. Meta applied rate-limiting after the disclosure and says no non-public data was exposed.
    This case raises important questions about phone numbers as identifiers and long-term privacy safeguards.
    Share your insights & follow for more security-focused analysis.

    #InfoSec #CyberSecurity #Privacy #DataExposure #WhatsApp #SecurityResearch #DigitalIdentity #TechNadu

  48. Researchers enumerated 3.5B WhatsApp phone numbers through the platform’s contact-discovery feature, revealing public profile photos and text for millions of users. Meta applied rate-limiting after the disclosure and says no non-public data was exposed.
    This case raises important questions about phone numbers as identifiers and long-term privacy safeguards.
    Share your insights & follow for more security-focused analysis.

    #InfoSec #CyberSecurity #Privacy #DataExposure #WhatsApp #SecurityResearch #DigitalIdentity #TechNadu

  49. Researchers enumerated 3.5B WhatsApp phone numbers through the platform’s contact-discovery feature, revealing public profile photos and text for millions of users. Meta applied rate-limiting after the disclosure and says no non-public data was exposed.
    This case raises important questions about phone numbers as identifiers and long-term privacy safeguards.
    Share your insights & follow for more security-focused analysis.

    #InfoSec #CyberSecurity #Privacy #DataExposure #WhatsApp #SecurityResearch #DigitalIdentity #TechNadu