[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f1q2vqo9f0yjfe":3},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":9,"domain":10,"breachDate":11,"addedDate":12,"modifiedDate":12,"contentUpdatedAt":13,"source":14,"sourceUrl":15,"sourceUrls":16,"pwnCount":18,"affectedCount":18,"affectedCountStatus":19,"affectedCountLowerBound":20,"affectedCountUnit":21,"hasEnglishDescription":4,"severity":22,"dataClasses":23,"description":32,"seoTitle":33,"seoTitleEn":34,"seoDescription":33,"seoDescriptionEn":35,"logoUrl":36,"isVerified":4,"isSensitive":37,"isSpamList":37,"isMalware":37,"company":38},"68e3266eda11adda488252b5","ModernBusinessSolutions","Modern Business Solutions Data Breach","modern-business-solutions","modbsolutions.com","2016-10-08T00:00:00.000Z","2016-10-12T09:09:11.000Z","2026-07-18T23:54:23.827Z","Verified breach record","https:\u002F\u002Fnews.softpedia.com\u002Fnews\u002Fhacker-steals-58-million-user-records-from-data-storage-provider-509190.shtml",[15,17],"https:\u002F\u002Farstechnica.com\u002Finformation-technology\u002F2016\u002F10\u002Fbreach-exposes-at-least-58-million-accounts-includes-names-jobs-and-more\u002F",58843488,"known",null,"unknown","Critical",[24,25,26,27,28,29,30,31],"Dates of birth","Email addresses","Genders","IP addresses","Job titles","Names","Phone numbers","Physical addresses","\u003Cp>The Modern Business Solutions data breach is a serious security incident that occurred in October 2016 when a large file of personal data associated with data storage and database hosting services was exposed online. The verified scope includes 58,843,488 unique email addresses. The dataset contains dates of birth, email addresses, genders, IP addresses, job titles, names, phone numbers, and physical addresses. Passwords, payment card information, bank account details, or government ID numbers are not among the verified data fields.\u003C\u002Fp>\u003Cp>The impact of this incident is broader than the visibility of a single piece of contact information. When a name, email, phone number, address, date of birth, and work information are linked to the same person, authentication questions, targeted fraud messages, fake delivery notifications, and work-focused social engineering attempts can become more convincing. The company's failure to publicly provide detailed explanations of why the data was present in its systems also requires limiting the scope assessment to careful and verified areas.\u003C\u002Fp>\u003Ch2>Leaking Data Types and Risks\u003C\u002Fh2>\u003Cp>Verified data categories include birth dates, email addresses, genders, IP addresses, job titles, names, phone numbers, and physical addresses. When these fields are evaluated together, a strong profile is formed regarding a person's real identity, communication channels, location, and work context. Address and phone information can be used for fraud calls, email addresses for phishing messages, and birth dates and physical addresses to predict authentication questions.\u003C\u002Fp>\u003Cp>Because the password has not been verified, this incident should not be seen directly as a password list. Nevertheless, the risk does not decrease; because when personal data matches passwords, usernames, or payment information from other leaks, the profile in the attacker's hands becomes more detailed. For individuals with job titles and employer context, fake offers, invoices, deliveries, recruitment, or customer service messages may appear more convincing.\u003C\u002Fp>\u003Ch2>Verified Scope and Boundaries\u003C\u002Fh2>\u003Cp>The scope is limited to the incident dated October 8, 2016, and 58,843,488 affected accounts. The domain is verified as modbsolutions.com. The addition and last modification time is October 12, 2016. Data classes are limited strictly to verified fields; password, payment card, bank account, social security number, health data, or official ID fields are not included.\u003C\u002Fp>\u003Cp>This incident is evaluated in the context of data storage and database hosting. To whom the data belongs, from which customers it comes, or under which business relationship it is held cannot be clearly determined for each user. Therefore, the explanation focuses on apparent personal data areas and the practical risk arising for the user, without amplifying ownership claims that are not confirmed.\u003C\u002Fp>\u003Ch2>User Groups at Risk\u003C\u002Fh2>\u003Cp>The first group at risk consists of people whose email address appears along with their phone number, physical address, and date of birth. For these users, fake delivery, banking, insurance, utility, customer support, or account verification messages can become more convincing. For individuals with a job title, fake supplier requests, business connection messages, or corporate payment change attempts pose a separate risk.\u003C\u002Fp>\u003Cp>The second group consists of users who use the same email address across different services and whose personal information has been exposed in other incidents in the past. When different data sets are combined, date of birth, address, phone number, and email come together; this makes account recovery questions, phone verification attempts, and identity association easier. The fact that the data is old does not mean it is secure, because fields like address and date of birth can remain valid for a long time.\u003C\u002Fp>\u003Ch2>Urgent Measures to Be Taken\u003C\u002Fh2>\u003Cp>The matched user should verify unexpected connection, delivery, document, payment, or account verification requests received via email and phone directly through a trusted secondary channel. Personal information should not be shared in messages that appear to come from banks, shipping companies, insurance, public services, or business relationships. The sign-in history, recovery addresses, and forwarding rules in the email account should be checked.\u003C\u002Fp>\u003Cp>Even if the password is not verified in this incident, if the same email is used on other services, account security should be further strengthened. Unique passwords, a password manager, and multi-factor authentication should be basic precautions. People whose phone numbers and addresses are exposed should also warn family members and colleagues against the possibility of fake calls and address-focused fraud.\u003C\u002Fp>\u003Ch2>Long-Term Security Strategies\u003C\u002Fh2>\u003Cp>In the long term, it is important to reduce the visibility of personal data. Users should clean up their old accounts and unnecessary profile fields, separate their email addresses according to their purposes, and not share their phone numbers with non-mandatory services. Persistent fields such as physical address, date of birth, and work information are difficult to change, so it should be accepted that this data could be used in social engineering attempts in the future.\u003C\u002Fp>\u003Cp>For institutions, the lesson is about data minimization and retention period auditing. When customer, candidate, employee, or third-party data sets are kept unnecessarily, a single breach incident can affect millions of people. Access rights, externally exposed service controls, data inventory, deletion policies, and incident reporting processes should be regularly reviewed.\u003C\u002Fp>\u003Ch2>Record Control and User Action\u003C\u002Fh2>\u003Cp>If a user sees a match, they should evaluate which fields are listed in order of priority. The email address can be used for phishing and account attempts, the phone number for fake calls, the physical address and date of birth for identity association, and the job title for corporate social engineering. Therefore, it is necessary to check not only one account but also other services linked with the same information.\u003C\u002Fp>\u003Cp>The Modern Business Solutions incident is a high-impact data breach that does not involve passwords but combines a large number of persistent personal fields. The long-term risk arising from this incident is significantly reduced when users complete the steps of using a unique password, strong email security, multi-factor authentication, verifying suspicious communications through a second channel, and minimizing unnecessary profile data.\u003C\u002Fp>","","Modern Business Solutions Data Breach (58.8 Million Reported Records)","Modern Business Solutions Data Breach. 58.8 Million reported records were reported. Reported data: Dates of birth, Email addresses, Genders. Review the scope…","\u002Fuploads\u002Flogo\u002Fmodbsolutions_com.webp",false,{"name":39,"sector":40,"country":41,"website":10,"websiteArchiveUrl":33,"websiteStatus":33,"websiteCheckedAt":20},"Modern Business Solutions","Data storage and database hosting","United States"]