Why Data Variety Can Matter More Than Breach Size.
16 November 2026A total of 22 breach events were found and analysed resulting in 2,293,752 exposed accounts containing a total of 44 different data types of personal datum. The breaches found publicly and freely available included GeekedIn, Deercase, Cheer Fan, Bureau of Internal Revenue (BIR) and ColorBox. Sign in to view the full
library of breach events which includes, where available, reference articles relating to
each breach.
Categories of Personal Data Discovered
Technology, Contact, Geolocation, Commerce, Sociodemographic, Digital Behaviour, Academic, National Identifiers, Unstructured, Career, Audio and Visual, Finance, Human Behaviour, Relationships.
Data breadth changes what an exposure can reveal
A record becomes more informative as different fields establish relationships between a person, account, organisation and activity. The relevant question is not simply how many data types were present. It is what those fields can reveal when considered together.For example, information might establish:
- Who somebody is
- How they can be contacted
- Where they live or work
- Which organisation they are connected to
- Which service or product they use
- What professional role or interest they have
- Which identifiers are used across other systems
These are general examples of how data can relate. They are not a description of the fields present in every event found this week.
The 44 data types were identified across all 22 events. Every account did not necessarily contain every type, and the same combination was not necessarily present in each event.
The BreachAware team has recorded and reviewed the provenance of this material. The descriptions shared here are intentionally limited, providing defenders with useful context without publishing source locations, detailed contents or information that could encourage misuse.
Not all personal data ages at the same rate
Some exposed information can be changed quickly. A password can be reset, a session revoked and a payment card replaced. Other information is considerably more persistent.A person may retain the same name, date of birth, professional history or government identifier for years. Historical addresses, employers and telephone numbers can also remain useful for linking records even after they stop being current.
This creates an important distinction between immediate remediation and long-term exposure.
A compromised password may justify urgent action but lose much of its value once it is changed. Persistent identity information may not provide direct access, but it can remain relevant to verification, impersonation and record matching for much longer.
Businesses should therefore avoid using “Can the customer change it?” as the only measure of impact.
Professional information can connect people to business roles
GeekedIn was associated with professional profiles containing information about users’ skills and experience. Its inclusion provides a useful example of how professional data can connect an individual to a particular function or area of expertise. [Mozilla Monitor provides historical context for the GeekedIn event](https://monitor.mozilla.org/en-GB/breach-details/GeekedIn).Professional information is often intentionally shared. That does not make every structured collection of it harmless.
A public profile may reveal one employment relationship. A combined record could potentially connect that profile with private contact details or identifiers used elsewhere.
For B2B organisations, this matters most where the person holds a sensitive role. Finance personnel, administrators, executives and technical specialists may warrant more attention than a record count alone would indicate.
This does not mean everyone with a specialist role will be targeted. It means role context should form part of a proportionate exposure assessment.
Personalisation can create data beyond a normal retail order
Deercase sells phone cases and accessories, including products customised with names, initials, messages and uploaded photographs. [Deercase describes its customisation services on its website](https://www.deercase.com/).This context does not establish that photographs, custom messages, delivery information or device details were present in the event.
It illustrates a wider issue for retailers offering personalised products: the information required to manufacture an item may differ from the information needed to maintain the customer account.
Once an order is complete, the business should consider whether uploaded creative material still needs to be retained, how long it should remain accessible and which employees or suppliers require access.
Data minimisation is not only about collecting fewer form fields. It also applies to customer-provided files and content created as part of delivering a service.
Government context requires particularly careful language
The Philippine Bureau of Internal Revenue is responsible for assessing and collecting national internal revenue taxes, fees and related charges. [The BIR describes its official mandate](https://www.bir.gov.ph/AgencyMandate).Its inclusion should not be interpreted as proof that tax returns, earnings, financial statements or particular government systems were present in the exposed event.
A government body can maintain public directories, administrative systems, service portals and many other datasets. The organisation’s mandate provides context, but it does not identify the affected source.
The appropriate response is to assess the verified fields rather than importing the sensitivity of the organisation’s entire function into every record associated with its name.
This avoids both understatement and unnecessary alarm.
Short labels should not become speculative identities
Cheer Fan and ColorBox are retained as the recorded source titles. Names such as ColorBox are used by multiple unrelated businesses and products. Expanding the title publicly without a clear need could associate the event with the wrong entity.Similarly, the phrase Cheer Fan should not be used to infer that athletes, children, schools or a particular sporting organisation were involved.
This does not question the provenance recorded by BreachAware. It reflects the distinction between having verified internal evidence and choosing how much identifying detail is useful to publish.
A high-level article can provide defensive insight without creating an unnecessarily detailed catalogue of exposed sources.
Four qualities determine how data should be assessed
A practical review can consider four characteristics of each verified data type.SensitivityCould the field reveal private circumstances, financial information, account access or another detail likely to cause harm if misused?
PersistenceCan the individual change it, or is it likely to remain associated with them for many years?
LinkabilityCan the field connect this record to another service, identity or organisation?
AuthorityDoes it relate to an account or person capable of approving payments, changing access or influencing an important process?
These qualities are more useful than applying the same severity rating to every field.
An email address may be low sensitivity in one context but highly linkable. A professional role may be publicly visible but still relevant to authority. An old password may be changeable but remain important if it was reused.
What the weekly totals do and do not show
The 2,293,752 exposed accounts should not be interpreted as the same number of unique or newly affected people. The total may include:- Historical or inactive accounts
- Several records belonging to the same person
- Duplicate records across events
- Information already circulated elsewhere
- Identifiers that have since changed ownership
The 44 data types describe the breadth of the week’s material, not the contents of every account.
The named examples also do not establish a trend affecting government, retail, professional or community services. They provide context from the wider group of events analysed during the week.
Three defensive checks for B2B organisations
1. Assess combinations rather than isolated fieldsWhen reviewing an exposure, consider how the verified fields relate to one another.
An email address alone may justify monitoring. The same address connected to a current job title, telephone number and recovery information may require a different response.
Document why a particular combination changes the assessment so decisions remain consistent and reviewable.
2. Separate immediate actions from persistent riskPasswords, sessions and active authentication details may require prompt containment.
Persistent personal information calls for different measures. These can include strengthening identity verification, warning relevant employees about plausible impersonation and ensuring static personal details are not treated as secret authenticators.
Avoid asking affected people to “change” information that cannot realistically be replaced.
3. Tailor notifications to the data that mattersA useful notification should explain the practical consequence of the verified data without reproducing unnecessary details from the source.
Tell people what they can do, what the organisation has done and which future communications deserve additional verification. Generic advice to change every password may be inappropriate where no credentials were present.
Proportionate guidance is more likely to be understood and acted upon.
The wider lesson
This week demonstrates why account volume and data breadth answer different questions.Volume indicates how much material was found. Data diversity helps explain what the material may reveal and how long its relevance could persist.
Neither measure should be used alone. A large collection may contain extensive duplication, while a smaller set of highly connected fields can create a clearer representation of the people involved.
For B2B defenders, the most useful question is not simply, “How many accounts were exposed?” It is, “Which combinations of data create a meaningful risk to our people, identities and business processes?”