<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>hackerlogs: Data Breaches</title>
    <link>https://hackerlogs.com/topics/data-breaches/</link>
    <atom:link href="https://hackerlogs.com/topics/data-breaches/rss.xml" rel="self" type="application/rss+xml" />
    <description>Confirmed breach disclosures, third-party vendor compromises, extortion claims, and the evidence separating verified exposure from leak-site pressure.</description>
    <language>en</language>
    <lastBuildDate>Sat, 21 Nov 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>Fandango Checkout Breach Exposed 69,665 Payment Cards.</title>
      <link>https://hackerlogs.com/blog/fandango-checkout-cards-69665/</link>
      <guid isPermaLink="true">https://hackerlogs.com/blog/fandango-checkout-cards-69665/</guid>
      <pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
      <dc:creator>Ajain Vivek</dc:creator>
      <description><![CDATA[<p>Fandango disclosed a checkout-page incident from 8 to 11 October 2026 exposed payment-card numbers, CVVs, expiration dates, billing ZIP codes, and email addresses for 69,665 people nationwide. Names and Social Security numbers were not involved. Fandango determined the breach on 30 October and began notifying customers on 13 November, offering credit monitoring through 13 February 2027.</p><p><strong>Key takeaways</strong></p><ul><li>Fandango reported 69,665 people affected nationwide, including 6,323 Texas residents, in its 17 November Texas AG filing.</li><li>Exposed data included payment-card number, CVV, expiration date, billing ZIP, and email address; first and last name, government ID, and SSN were not involved, the letter says.</li><li>The breach window ran from 8 to 11 October 2026, affecting checkout customers during those four days. Fandango determined the incident on 30 October.</li><li>Fandango filed with California AG on 13 November (14 days from determination), meeting the state's 30-day statute, and with Texas on 17 November (18 days), well within the 60-day limit.</li><li>IDX credit and identity monitoring is offered to affected customers through 13 February 2027.</li></ul>]]></description>
      <category>data-breaches</category>
    </item>
    <item>
      <title>Peach Aviation Confirms 8.99 Million Records Leaked Through Email Vendor.</title>
      <link>https://hackerlogs.com/blog/peach-aviation-yumirulink-8997106/</link>
      <guid isPermaLink="true">https://hackerlogs.com/blog/peach-aviation-yumirulink-8997106/</guid>
      <pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
      <dc:creator>Ajain Vivek</dc:creator>
      <description><![CDATA[<p>Peach Aviation disclosed on 20 November 2026 that unauthorized access to Yumirulink's Cuenote FC email service exposed 8,997,106 customer records including names, birth dates, gender, addresses, phone numbers, email addresses, and itinerary details. Credit-card and passport data were not involved. The intrusion occurred on 18 October; Yumirulink shut down all Cuenote FC functions, and affected services remain suspended.</p><p><strong>Key takeaways</strong></p><ul><li>Peach Aviation reported 8,997,106 customer records exposed through Yumirulink's Cuenote FC email platform, which handles newsletters, automated notifications, and airport refund forms.</li><li>Exposed data includes name, date of birth, gender, address, phone number, email address, and itinerary details. Credit-card and passport information was not involved.</li><li>The intrusion was detected on 18 October 2026 at Yumirulink's server environment. Yumirulink shut down the servers and suspended all Cuenote FC functions as an emergency measure.</li><li>Peach confirmed the scope of affected customer information on 6 November after Yumirulink reported which services were impacted.</li><li>No secondary damage or misuse of the exposed information has been confirmed yet, but Peach warns customers of possible phishing attempts using their real data.</li></ul>]]></description>
      <category>data-breaches</category>
    </item>
    <item>
      <title>Plaid KARTE Breach Hit 570 Client Companies Across Japan.</title>
      <link>https://hackerlogs.com/blog/plaid-karte-japan-570-clients/</link>
      <guid isPermaLink="true">https://hackerlogs.com/blog/plaid-karte-japan-570-clients/</guid>
      <pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
      <dc:creator>Ajain Vivek</dc:creator>
      <description><![CDATA[<p>On 13 November 2026, an attacker exploited a vulnerability in Plaid's KARTE platform, exfiltrating data from 570 client companies across Japan, including MUFG, SMBC, ZOZO, Marui, Suntory, DHC, Sharp, Canon Marketing, Goldwin, Recruit, and J.League. Clients reported over 140 million exposed records. Plaid shut KARTE down fully and targets a staged restart in mid-January 2027.</p><p><strong>Key takeaways</strong></p><ul><li>Plaid confirmed 570 companies whose customer data loaded into KARTE leaked, 487 whose user-behaviour records leaked, and 754 whose external-service credentials leaked.</li><li>Clients reported over 140 million exposed records total, including 15.18 million ZOZO customers, 14 million SMBC records, 19.11 million DHC records, and 18.29 million JINS accounts.</li><li>MUFG Bank reported 6.5 million records with gender, age, and prefecture; SMBC reported 14 million with birth dates, age bands, and gender, both without names or contact details.</li><li>The attacker exploited a vulnerability in a public data-retrieval route on 13 November, stole credentials, and logged into KARTE's admin console before Plaid detected and shut down at 14:27 Japan time.</li><li>Plaid admitted data from former clients who ended their contracts was still stored due to failures in human operations and should have been deleted under its terms.</li></ul>]]></description>
      <category>data-breaches</category>
    </item>
    <item>
      <title>RIKEN Confirms 430 Credentials Stolen From Fugaku Supercomputer Users.</title>
      <link>https://hackerlogs.com/blog/riken-fugaku-430-ssh-keys/</link>
      <guid isPermaLink="true">https://hackerlogs.com/blog/riken-fugaku-430-ssh-keys/</guid>
      <pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
      <dc:creator>Ajain Vivek</dc:creator>
      <description><![CDATA[<p>RIKEN confirmed on 20 November 2026 that an attacker who breached Fugaku and RIKYU supercomputers between 10 and 13 November exfiltrated 430 authentication credentials from user home directories, including SSH private keys for external systems. Of these, 233 had no passphrase and 197 had passphrases. RIKEN is treating all 430 as compromised and asking users to revoke and reissue keys.</p><p><strong>Key takeaways</strong></p><ul><li>RIKEN confirmed 430 authentication credentials were collected and exfiltrated from Fugaku user home directories, including SSH private keys for external systems.</li><li>Of the 430 credentials, 233 private keys had no passphrase and 197 had passphrases. RIKEN found traces of external connections using some credentials but no other confirmed misuse.</li><li>Personal data of 4,222 Fugaku users may be compromised, including names, email addresses, user IDs, address, affiliation, phone numbers, and identity-document types, but not the documents themselves.</li><li>The attacker exploited a vulnerability in a web dashboard exposed to the internet between 10 and 13 November, gaining a foothold into the internal operations network.</li><li>Fugaku was shut down at 04:30 on 14 November and remains offline. RIKEN is rebuilding servers, separating public services from the admin network, and establishing an external investigative committee.</li></ul>]]></description>
      <category>data-breaches</category>
    </item>
    <item>
      <title>Zurich Insurance Hong Kong Portal Hit. 38,453 People May Be Affected.</title>
      <link>https://hackerlogs.com/blog/zurich-insurance-hk-portal-38453/</link>
      <guid isPermaLink="true">https://hackerlogs.com/blog/zurich-insurance-hk-portal-38453/</guid>
      <pubDate>Sat, 21 Nov 2026 00:00:00 GMT</pubDate>
      <dc:creator>Ajain Vivek</dc:creator>
      <description><![CDATA[<p>Zurich Hong Kong disclosed on 19 November 2026 that its customer portal was accessed without authorization. The Privacy Commissioner said 38,453 people may be affected across three Zurich entities. Exposed information includes names, Hong Kong ID and passport numbers, birth dates, email, phone, and policy details. Bank accounts, credit cards, and passwords were not involved.</p><p><strong>Key takeaways</strong></p><ul><li>Hong Kong's Office of the Privacy Commissioner said 38,453 people may be affected, and it opened investigations into three Zurich entities that reported the incident.</li><li>Possible exposed information includes names, Hong Kong ID and passport numbers, dates of birth, email addresses, phone numbers, and policy information. Bank accounts and credit cards were not involved.</li><li>Zurich detected the unauthorized access on 17 November 2026 and took the customer portal offline temporarily for system maintenance. The start date of the intrusion has not been disclosed.</li><li>Zurich is investigating with cybersecurity experts, notifying affected customers, and has reported the incident to regulatory authorities.</li><li>Existing insurance policies remain active and unaffected by the breach.</li></ul>]]></description>
      <category>data-breaches</category>
    </item>
    <item>
      <title>Bandai Logipal Breach Exposes 413,527 Ichiban Kuji Delivery Records</title>
      <link>https://hackerlogs.com/blog/bandai-logipal-ichiban-kuji-413527/</link>
      <guid isPermaLink="true">https://hackerlogs.com/blog/bandai-logipal-ichiban-kuji-413527/</guid>
      <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
      <dc:creator>Ajain Vivek</dc:creator>
      <description><![CDATA[<p>Bandai Logipal, Bandai Namco's logistics subsidiary, suffered unauthorized access in October 2026 exposing 413,527 Ichiban Kuji delivery records containing names, addresses, and phone numbers. The breach included 387,895 Ichiban Kuji ONLINE records (2025-2026) and 25,632 Ichiban Kuji Club campaign records (2019-2026). No credit card data was involved.</p><p><strong>Key takeaways</strong></p><ul><li>Bandai Logipal found unauthorized access traces on October 21, 2026 and confirmed company account misuse, affecting logistics system servers holding Ichiban Kuji delivery data.</li><li>Total of 413,527 delivery records may have leaked: 387,895 from Ichiban Kuji ONLINE (January 2025-October 2026) and 25,632 from Ichiban Kuji Club campaigns (January 2019-October 2026).</li><li>Information exposed includes names, addresses, and phone numbers for customers who received product shipments, but no credit card information was involved.</li><li>The shipping system was stopped October 24-28, 2026 for investigation and recovery, with affected customers receiving notifications starting November 17, 2026.</li></ul>]]></description>
      <category>data-breaches</category>
    </item>
    <item>
      <title>Bell Financial Group Reports Unauthorized Access to Client Data</title>
      <link>https://hackerlogs.com/blog/bell-financial-australia-breach/</link>
      <guid isPermaLink="true">https://hackerlogs.com/blog/bell-financial-australia-breach/</guid>
      <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
      <dc:creator>Ajain Vivek</dc:creator>
      <description><![CDATA[<p>Bell Financial Group, an ASX-listed financial services firm with A$92.1 billion in funds under advice, disclosed on November 20, 2026 that unauthorized access to a limited number of IT systems resulted in some client data being accessed. The incident has been contained, client assets remain safe, and the company is investigating with cybersecurity specialists.</p><p><strong>Key takeaways</strong></p><ul><li>Bell Financial Group disclosed unauthorized access to a limited number of IT systems on November 20, 2026, with the incident now contained.</li><li>The firm manages A$92.1 billion in funds under advice and confirmed client assets remain safe despite the data security incident.</li><li>Bell Financial notified the Australian Cyber Security Centre, Australian Federal Police, and engaged with the Office of the Australian Information Commissioner.</li><li>The company did not disclose the number of affected clients, types of data accessed, or the timing of the unauthorized access.</li></ul>]]></description>
      <category>data-breaches</category>
    </item>
    <item>
      <title>Chase, Visa, Mastercard Data Exposed in Qubole Vendor Breach</title>
      <link>https://hackerlogs.com/blog/chase-visa-mastercard-qubole-vendor/</link>
      <guid isPermaLink="true">https://hackerlogs.com/blog/chase-visa-mastercard-qubole-vendor/</guid>
      <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
      <dc:creator>Ajain Vivek</dc:creator>
      <description><![CDATA[<p>In November 2026, JPMorgan Chase, Visa, and Mastercard confirmed third-party service providers were breached, exposing customer marketing data including names, email addresses, and phone numbers. The n0n ransomware group claimed responsibility for attacking Qubole, a cloud analytics provider, using compromised AWS credentials to access customer environments between October 14 and 26, 2026.</p><p><strong>Key takeaways</strong></p><ul><li>JPMorgan Chase disclosed attackers accessed marketing data from third-party vendors, including approximately 16,000 Reserve credit card customer email addresses and some phone numbers.</li><li>Visa confirmed a service provider in Asia-Pacific was breached but no payment data such as card numbers were affected, only marketing information.</li><li>The n0n ransomware group claimed responsibility for breaching Qubole, a cloud data analytics company, by compromising AWS IAM credentials between October 14-26, 2026.</li><li>Researchers analyzing leaked files found no card numbers, passwords, or home addresses, but the data could enable phishing attacks posing as concierge or banking services.</li></ul>]]></description>
      <category>data-breaches</category>
    </item>
    <item>
      <title>KPMG Canada Client Tax Documents Accessed in Cyber Breach</title>
      <link>https://hackerlogs.com/blog/kpmg-canada-tax-documents-breach/</link>
      <guid isPermaLink="true">https://hackerlogs.com/blog/kpmg-canada-tax-documents-breach/</guid>
      <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
      <dc:creator>Ajain Vivek</dc:creator>
      <description><![CDATA[<p>KPMG Canada confirmed on November 18, 2026 that a third party gained unauthorized access to some clients' tax documents in a cybersecurity incident. The firm secured its systems and is contacting affected clients, but did not disclose how many clients were affected, the number of files accessed, when the breach occurred, or the attack method used to infiltrate its systems.</p><p><strong>Key takeaways</strong></p><ul><li>KPMG Canada confirmed on November 18, 2026 that some client tax documents were accessed but did not disclose the number of affected clients or files.</li><li>The breach follows at least four major Bay Street law firms being hit by vishing attacks where hackers posed as IT support to gain access to client files.</li><li>The Canadian Centre for Cyber Security warned in October 2026 about ongoing voice phishing targeting legal and financial sector organizations since January.</li><li>KPMG stated it is confident the accessed information is not available online or being misused, though security analysts caution this may be premature.</li></ul>]]></description>
      <category>data-breaches</category>
    </item>
    <item>
      <title>Mitsui Shopping Park App Breached, Point Member Data Leaked</title>
      <link>https://hackerlogs.com/blog/mitsui-shopping-park-app-breach/</link>
      <guid isPermaLink="true">https://hackerlogs.com/blog/mitsui-shopping-park-app-breach/</guid>
      <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
      <dc:creator>Ajain Vivek</dc:creator>
      <description><![CDATA[<p>Mitsui Fudosan confirmed on November 19, 2026 that unauthorized access to the Mitsui Shopping Park app leaked point members' numbers, names, birth dates, addresses, and email addresses. The app was stopped November 18 for investigation. Credit card information and passwords were not involved.</p><p><strong>Key takeaways</strong></p><ul><li>Mitsui Fudosan and Mitsui Fudosan Retail Management confirmed unauthorized access to the Mitsui Shopping Park app on November 18, 2026, with personal data leakage confirmed before service suspension.</li><li>Leaked information includes point member numbers, names, birth dates, addresses, and email addresses, but excludes credit card information and passwords.</li><li>The app was suspended November 18, 2026 to prevent further damage, with the specific intrusion route and affected customer count still under investigation.</li><li>Physical stores, online shopping sites, and alternative point accumulation methods remain operational while the app undergoes security review.</li></ul>]]></description>
      <category>data-breaches</category>
    </item>
    <item>
      <title>Momo Taiwan Detects Unauthorized Access to Mo Store Plus Data</title>
      <link>https://hackerlogs.com/blog/momo-taiwan-mo-store-plus-breach/</link>
      <guid isPermaLink="true">https://hackerlogs.com/blog/momo-taiwan-mo-store-plus-breach/</guid>
      <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
      <dc:creator>Ajain Vivek</dc:creator>
      <description><![CDATA[<p>Momo Taiwan detected on November 18, 2026 during routine monitoring that some shipping data in its mo store plus third-party marketplace service was accessed without authorization. The company immediately isolated the affected system, blocked access, and notified about 350,000 potentially affected customers as a precaution. Member passwords, credit card numbers, and payment information were not involved.</p><p><strong>Key takeaways</strong></p><ul><li>Momo detected unauthorized access to some mo store plus shipping data on November 18, 2026 during routine system monitoring and immediately blocked access.</li><li>About 350,000 customers will be notified as a precautionary measure, though this count does not equal confirmed data leakage numbers.</li><li>The company confirmed member account passwords, credit card numbers, and other payment information were not involved in the incident.</li><li>Mo store plus operates on an independent system and the breach was contained to some shipping data, with other services unaffected.</li></ul>]]></description>
      <category>data-breaches</category>
    </item>
    <item>
      <title>N-able Server Breach Disrupts Mail Assure Services Across Three Regions</title>
      <link>https://hackerlogs.com/blog/n-able-mail-assure-server-breach/</link>
      <guid isPermaLink="true">https://hackerlogs.com/blog/n-able-mail-assure-server-breach/</guid>
      <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
      <dc:creator>Ajain Vivek</dc:creator>
      <description><![CDATA[<p>N-able confirmed on November 18, 2026 that unauthorized actors accessed a single web server in Mail Assure and SpamExperts Hosted Cloud, causing management portals, APIs, and logging to be disabled across Americas, Europe, and APAC. Email delivery and filtering remained operational. No evidence of customer data or mailbox access was found.</p><p><strong>Key takeaways</strong></p><ul><li>N-able confirmed on November 18, 2026 that attackers accessed one web server where certain credentials may have been exposed, causing service disruption starting November 16.</li><li>Management portals, APIs, quarantine, logging, and mailbox synchronization were disabled across Americas, Europe, and APAC while core mail flow and filtering stayed operational.</li><li>N-able took the server offline, rotated internal credentials, revoked customer API tokens, invalidated OAuth tokens, and reset local user passwords as containment measures.</li><li>As of November 20, 2026, investigation found no evidence that customer data or tenant mailboxes were accessed, but restoration remained pending security validation.</li></ul>]]></description>
      <category>data-breaches</category>
    </item>
    <item>
      <title>New Zealand Defence Force Database Accessed in Cyber Incident</title>
      <link>https://hackerlogs.com/blog/nz-defence-force-force4families-breach/</link>
      <guid isPermaLink="true">https://hackerlogs.com/blog/nz-defence-force-force4families-breach/</guid>
      <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
      <dc:creator>Ajain Vivek</dc:creator>
      <description><![CDATA[<p>The New Zealand Defence Force confirmed on November 20, 2026 that unauthorized access affected its public websites and a Force4Families Defence Discounts database containing registered users' names and email addresses. The NZDF was notified by its website provider on Friday morning, removed affected websites from service, and began a forensic investigation while contacting affected individuals.</p><p><strong>Key takeaways</strong></p><ul><li>NZDF confirmed on November 20, 2026 that a database associated with the Force4Families Defence Discounts scheme containing names and email addresses was accessed.</li><li>The Defence Force was notified by its website provider on Friday morning of unauthorized access to its website systems and took affected websites offline.</li><li>Affected individuals have been contacted and given advice on protecting themselves from phishing emails, scams, and unsolicited requests.</li><li>The Privacy Commissioner has been informed and investigations continue to determine the full extent of information affected.</li></ul>]]></description>
      <category>data-breaches</category>
    </item>
    <item>
      <title>Osaki Electric Hit by Qilin Ransomware via VPN Without MFA</title>
      <link>https://hackerlogs.com/blog/osaki-electric-qilin-ransomware/</link>
      <guid isPermaLink="true">https://hackerlogs.com/blog/osaki-electric-qilin-ransomware/</guid>
      <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
      <dc:creator>Ajain Vivek</dc:creator>
      <description><![CDATA[<p>Osaki Electric was hit by Qilin ransomware on November 15, 2026, when attackers likely gained access around 1:30 a.m. through a VPN account that lacked multi-factor authentication. The November 20 second report confirmed attackers used repeated password attempts to bypass authentication, encrypted virtual servers, and posted technical information online, forcing the company to halt smart meter production indefinitely.</p><p><strong>Key takeaways</strong></p><ul><li>Osaki Electric confirmed attackers gained access on November 15, 2026 at approximately 1:30 a.m. through repeated password attempts on a VPN account without multi-factor authentication.</li><li>Some virtual servers were encrypted and technical information believed to be from Osaki systems was posted on a website that appears to belong to the Qilin ransomware group.</li><li>The attack forced Osaki to halt smart meter production and shipments at its Saitama works and two production subsidiaries with no announced restart date.</li><li>Backup data remains intact and recovery is under way, but Osaki has not disclosed the financial impact or timeline for resuming operations.</li></ul>]]></description>
      <category>data-breaches</category>
    </item>
    <item>
      <title>Payどん Kagoshima Payment App Shut Down After Vendor Breach of 251,172 Records</title>
      <link>https://hackerlogs.com/blog/paydon-kagoshima-vendor-breach-251172/</link>
      <guid isPermaLink="true">https://hackerlogs.com/blog/paydon-kagoshima-vendor-breach-251172/</guid>
      <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
      <dc:creator>Ajain Vivek</dc:creator>
      <description><![CDATA[<p>Payどん shut down all services on November 20, 2026 at 6:20 AM after vendor Infcurion's Wallet Station was breached on November 19, exposing 251,172 records including member information, account details, point balances, and transaction histories. Attack routes were blocked but restoration remains indefinite.</p><p><strong>Key takeaways</strong></p><ul><li>Payどん stopped all services November 20, 2026 at 6:20 AM after receiving reports that Infcurion's Wallet Station payment system was breached on November 19.</li><li>Total of 251,172 records leaked including member information (names, birth dates, phone numbers, emails, passwords), payment methods, point balances, and transaction histories with store names.</li><li>Infcurion detected mass access on November 19 evening, blocked attack sources, applied emergency patches, and shut down Payどん's system to prevent further damage.</li><li>Service restoration timeline remains undetermined pending comprehensive security review, with affected customers to receive individual notifications once investigation completes.</li></ul>]]></description>
      <category>data-breaches</category>
    </item>
    <item>
      <title>Japan FSA Orders Rakuten Securities to Report on Data Leak Affecting 4.47 Million</title>
      <link>https://hackerlogs.com/blog/rakuten-securities-fsa-order-447-million/</link>
      <guid isPermaLink="true">https://hackerlogs.com/blog/rakuten-securities-fsa-order-447-million/</guid>
      <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
      <dc:creator>Ajain Vivek</dc:creator>
      <description><![CDATA[<p>On November 19, 2026, Japan's Financial Services Agency ordered Rakuten Securities to submit a report concerning a possible customer information leak affecting up to 4.47 million accounts. The leaked data may include names, addresses, employers, financial institution account numbers, annual income, and financial assets accessed from a test server.</p><p><strong>Key takeaways</strong></p><ul><li>Japan's FSA issued a report order on November 19, 2026 to Rakuten Securities under financial and privacy laws over a possible leak affecting up to 4.47 million accounts.</li><li>Login IDs for approximately 11.25 million customer accounts may have been leaked, along with detailed personal and financial information from a test server.</li><li>The leaked data may include names, addresses, employers, financial institution account numbers, annual income, and financial assets.</li><li>The FSA order is considered unusual for unauthorized access incidents at financial institutions in Japan, reflecting the scale and sensitivity of the exposed data.</li></ul>]]></description>
      <category>data-breaches</category>
    </item>
    <item>
      <title>Rokkatei Online Shop Hit by Web Skimming Attack Exposing 8,000 Cards</title>
      <link>https://hackerlogs.com/blog/rokkatei-web-skimming-8000-cards/</link>
      <guid isPermaLink="true">https://hackerlogs.com/blog/rokkatei-web-skimming-8000-cards/</guid>
      <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
      <dc:creator>Ajain Vivek</dc:creator>
      <description><![CDATA[<p>Rokkatei's online shop checkout was tampered with from October 21 to November 18, 2026, allowing entered card details including full numbers, CVV codes, expiry dates, and cardholder names to be sent externally. About 8,000 transactions may be affected. The shop was shut down after discovery.</p><p><strong>Key takeaways</strong></p><ul><li>Rokkatei discovered on November 18, 2026 that third-party attackers had tampered with the online shop checkout, creating a window for card skimming from October 21, 21:00 to November 18, 11:00.</li><li>Full card numbers, cardholder names, expiry dates, and security codes for approximately 8,000 transactions may have been skimmed during input, even though Rokkatei does not store card data.</li><li>The company shut down the online shop immediately upon discovery and reported the incident to the Personal Information Protection Commission while investigating the scope.</li><li>Rokkatei confirmed no card misuse has been detected so far, but customers are advised to check statements and beware of phishing using the stolen data.</li></ul>]]></description>
      <category>data-breaches</category>
    </item>
    <item>
      <title>SBC Medical Group Breach Exposes 1.6 Million Customer Records</title>
      <link>https://hackerlogs.com/blog/sbc-medical-group-breach-1624000/</link>
      <guid isPermaLink="true">https://hackerlogs.com/blog/sbc-medical-group-breach-1624000/</guid>
      <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
      <dc:creator>Ajain Vivek</dc:creator>
      <description><![CDATA[<p>On November 16, 2026, attackers accessed SBC Medical Group's Japan website databases, stealing personal data for 1.624 million people including names, contact details, passwords, and treatment information covering 2010-2023. Separately, unauthorized access to the Tribeau booking platform used by 56 SBC-managed clinics affected approximately 19,000 individuals. No electronic medical records or mySBC reservation site data was confirmed accessed.</p><p><strong>Key takeaways</strong></p><ul><li>Basic personal information for 1.624 million individuals was stolen (2010-2023), including names, contact details, passwords, addresses, dates of birth, and patient card numbers.</li><li>Employee account information for approximately 20,000 records was obtained, with 459 employees having sensitive employment information including bank accounts and tax data exposed.</li><li>A separate incident at Tribeau booking platform affected about 19,000 individuals across 56 clinics with reservation and treatment information accessed.</li><li>SBC confirmed no unauthorized acquisition of electronic medical records or mySBC reservation site data, and no evidence of data misuse as of November 18, 2026.</li></ul>]]></description>
      <category>data-breaches</category>
    </item>
    <item>
      <title>Coles Confirms Cyber Incident Under Investigation, No Data Breach Evidence Yet.</title>
      <link>https://hackerlogs.com/blog/coles-cyber-incident-investigating/</link>
      <guid isPermaLink="true">https://hackerlogs.com/blog/coles-cyber-incident-investigating/</guid>
      <pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate>
      <dc:creator>Ajain Vivek</dc:creator>
      <description><![CDATA[<p>Coles, Australia's second-largest supermarket retailer, said in an ASX filing on 16 November 2026 that it is investigating a cyber incident. The company is working with the Australian Cyber Security Centre to contain and secure its IT environment and has found no evidence that customer, team, or supplier data was compromised. Stores and online shopping continue to operate.</p><p><strong>Key takeaways</strong></p><ul><li>Coles confirmed a cyber incident under investigation in an ASX filing on the morning of 16 November 2026.</li><li>The company is working with the Australian Cyber Security Centre (ACSC) to contain and secure systems.</li><li>No evidence of customer, team, or supplier data being taken has been found so far.</li><li>Store operations and online shopping continue without disruption.</li><li>How the incident happened remains undisclosed at this stage.</li></ul>]]></description>
      <category>data-breaches</category>
    </item>
    <item>
      <title>Woolworths Investigating After Dozens Report WISH Gift Cards Drained.</title>
      <link>https://hackerlogs.com/blog/woolworths-wish-gift-cards-drained/</link>
      <guid isPermaLink="true">https://hackerlogs.com/blog/woolworths-wish-gift-cards-drained/</guid>
      <pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate>
      <dc:creator>Ajain Vivek</dc:creator>
      <description><![CDATA[<p>Woolworths confirmed it is investigating after dozens of customers reported their digital WISH gift cards were spent without authorization. According to ABC News, some customers lost up to $500, with cards being spent at stores in other states. Woolworths has not said how the cards were accessed or whether a breach is suspected.</p><p><strong>Key takeaways</strong></p><ul><li>Woolworths is investigating reports from dozens of customers whose WISH gift cards were drained.</li><li>ABC News reported some customers lost up to $500, with cards spent at stores in different states.</li><li>Woolworths has not disclosed how the cards were accessed or whether a data breach occurred.</li><li>Customers should check their Everyday Gifting card balances and report unknown spends to giftcard@customerservice.woolworths.com.au.</li><li>The company has not confirmed the scale of affected customers or the investigation timeline.</li></ul>]]></description>
      <category>data-breaches</category>
    </item>
    <item>
      <title>La Poste Confirms Maileva Breach Exposed 22 Million People.</title>
      <link>https://hackerlogs.com/blog/laposte-maileva-22m-mail-breach/</link>
      <guid isPermaLink="true">https://hackerlogs.com/blog/laposte-maileva-22m-mail-breach/</guid>
      <pubDate>Sun, 15 Nov 2026 00:00:00 GMT</pubDate>
      <dc:creator>Ajain Vivek</dc:creator>
      <description><![CDATA[<p>Maileva, the business mail subsidiary of La Poste's Docaposte, confirmed in mid-November 2026 that a September 2026 cyberattack exposed names and postal addresses of 22 million distinct individuals across 39 million mail references. First suspicious activity dates to 9 September, before a 23 to 29 September shutdown. Frandroid reports business client IBANs and invoice amounts were also exposed.</p><p><strong>Key takeaways</strong></p><ul><li>Maileva confirmed 39 million mail references deduplicated to 22 million distinct individuals with exposed names and postal addresses.</li><li>An internal Docaposte timeline cited by Frandroid places first suspicious activity on 9 September, detection on 16-17 September, and system shutdown from 23 to 29 September.</li><li>Thousands of Maileva client organizations across social housing, healthcare, and public services are affected, and each client must notify its own recipients.</li><li>Frandroid reports Maileva's billing tool also exposed business client IBANs, invoice amounts, and accounting contacts, creating supplier fraud risk.</li><li>CNIL has been notified and a judicial inquiry is open. No public dump or resale of the full dataset has been established yet.</li></ul>]]></description>
      <category>data-breaches</category>
    </item>
    <item>
      <title>Extortion Group n0n Claims 10 Brands. None Has Confirmed a Breach.</title>
      <link>https://hackerlogs.com/blog/n0n-leak-site-claims-unconfirmed/</link>
      <guid isPermaLink="true">https://hackerlogs.com/blog/n0n-leak-site-claims-unconfirmed/</guid>
      <pubDate>Sun, 15 Nov 2026 00:00:00 GMT</pubDate>
      <dc:creator>Ajain Vivek</dc:creator>
      <description><![CDATA[<p>On 14 November 2026, extortion group n0n listed about 10 companies on its leak site, including Samsung, Starbucks, Timberland, Gap, VF Corporation, Alo Yoga, Airport Appliance and Steeden Financial. These are unverified claims. None of the named companies has confirmed a breach, and the size and authenticity of the claimed data are unknown.</p><p><strong>Key takeaways</strong></p><ul><li>n0n named about 10 companies on its leak site on 14 November 2026, days after claiming nearly 1 billion Expedia traveler records.</li><li>Trackers list Samsung, Starbucks, Timberland, Gap, VF Corporation, Alo Yoga, Airport Appliance, Steeden Financial, Pollstar and MM Insurance Agency.</li><li>For Samsung, n0n claims US Smart TV viewing records and household-level geographic data. Trackers mark the claim as pending verification.</li><li>None of the listed companies has confirmed a compromise. Treat every entry as an extortion claim until the company says otherwise.</li><li>Expect phishing that name-drops your account, loyalty profile or purchases with these brands.</li></ul>]]></description>
      <category>data-breaches</category>
    </item>
  </channel>
</rss>
