TCC
Company Details
Linkedin ID:
texoma-community-center
Website:
Employees number:
104
Number of followers:
256
NAICS:
62133
Industry Type:
Homepage:
texomacc.org
IP Addresses:
0
Company ID:
TEX_2086901
Scan Status:
In-progress
TEXOMA COMMUNITY CENTER Company CyberSecurity Posture
texomacc.org
TEXOMA COMMUNITY CENTER is a mental health care company based out of PO BOX 1087, SHERMAN, Texas, United States.
TEXOMA COMMUNITY CENTER A.I CyberSecurity Scoring
TCC Risk Score (AI oriented)Between 700 and 749
TCC
Updated:
- Powered by our proprietary A.I cyber incident model
- Insurance preferes TPRM score to calculate premium
TCC Global Score (TPRM)XXXX
TCC
- Instant access to detailed risk factors
- Benchmark vs. industry & size peers
- Vulnerabilities
- Findings
TCC Company CyberSecurity News & History
Past Incidents
1
Attack Types
1
TEXOMA COMMUNITY CENTER
Data Leak
Rankiteo Explanation
Attack with significant impact with internal employee data leaks
Description: Texoma Community Center in Texas (TCC) suffered a data breach incident involving a hack of email that affected about 24,030 patients. The incident involved unauthorized access between September 24, 2020 and December 1, 2020 to several email accounts. The compromised information included name, date of birth, medical history, treatment or diagnosis, health information, health insurance information including policy and/or subscriber information, insurance application and/or claims information, birth certificate, marriage certificate, digital signature, facial photograph, email address and password, unique biometric data, vehicle identification number, username and password, military identification number, and for a smaller number of individuals may include social security number.
TCC Company Scoring based on AI Models
Cyber Incidents Likelihood 3 - 6 - 9 months
A.I Risk Score Likelihood 3 - 6 - 9 months
Underwriter Stats for TCC
Incidents vs Mental Health Care Industry Average (This Year)
No incidents recorded for TEXOMA COMMUNITY CENTER in 2025.
Incidents vs All-Companies Average (This Year)
No incidents recorded for TEXOMA COMMUNITY CENTER in 2025.
Incident Types TCC vs Mental Health Care Industry Avg (This Year)
No incidents recorded for TEXOMA COMMUNITY CENTER in 2025.
Incident History — TCC (X = Date, Y = Severity)
TCC cyber incidents detection timeline including parent company and subsidiaries
TCC Company Subsidiaries
TEXOMA COMMUNITY CENTER is a mental health care company based out of PO BOX 1087, SHERMAN, Texas, United States.
Loading...
TCC Similar Companies
Parnassia Groep
Parnassia Groep is er voor uw gezondheid, dat doen wij met ruim 8.000 medewerkers. Zij zijn werkzaam op 560 locaties, die u vindt vooral in onze drie kernregio's Noord-Holland, Haaglanden, Rijnmond (waaronder de Zuid-Hollandse Eilanden). Welk psychisch of psychiatrisch probleem u ook heeft, wij h
.png)
TCC CyberSecurity News
December 05, 2025 01:17 PM
Rockwell Launches Industrial Cybersecurity Suite of Software and Services
The software and services combination offers end-to-end protection for regulated industrial systems and vulnerability management across vendor ecosystems.
December 05, 2025 01:14 PM
Global cybersecurity agencies publish secure AI integration principles for OT
U.S. and Australian cybersecurity agencies, together with international partners, have released new secure AI integration principles for OT...
December 05, 2025 01:00 PM
The 10 Hottest Cybersecurity Startups Of 2025
Our picks for the hottest cybersecurity startups of 2025 include companies in key categories such as AI security and agentic-powered cyber...
December 05, 2025 11:00 AM
DataKrypto’s 2026 Predictions and Trends
Today, we're sharing our 2026 Cybersecurity Predictions, offering our insights into the trends that we believe will be front and center in...
December 05, 2025 11:00 AM
$10.5 Bn Enterprise Data Loss Prevention Market - Forecasts
The enterprise DLP market offers significant opportunities driven by increased cybersecurity threats, growing data volumes,...
December 05, 2025 11:00 AM
Cybersecurity News: Predator spyware, Russia blocks FaceTime, US cyber strategy coming
Predator spyware, Russia blocks FaceTime, US cyber strategy coming, Brothers arrested for deleting government databases.
December 05, 2025 10:54 AM
Don’t Miss the Fortinet Cybersecurity Workshop at the ARC Forum
A Fortinet-led workshop at the ARC Industry Leadership Forum will focus on operationalizing cyber resilience to strengthen OT security and...
December 05, 2025 10:26 AM
Securing Custom Code Inside a No-Code Website Builder
No-code builders offer opportunities to create complex websites without programming. Though the businesses grow and their requirements...
December 05, 2025 10:11 AM
Cybersecurity Advances Strengthen Protection in Online Gambling Infrastructure
Online gambling sites now process upwards of 12 million transactions each day, a staggering number that puts a giant target on their backs...
Frequently Asked Questions
Explore insights on cybersecurity incidents, risk posture, and Rankiteo's assessments.
TCC CyberSecurity History Information
Official Website of TEXOMA COMMUNITY CENTER
The official website of TEXOMA COMMUNITY CENTER is http://texomacc.org.
TEXOMA COMMUNITY CENTER’s AI-Generated Cybersecurity Score
According to Rankiteo, TEXOMA COMMUNITY CENTER’s AI-generated cybersecurity score is 731, reflecting their Moderate security posture.
How many security badges does TEXOMA COMMUNITY CENTER’ have ?
According to Rankiteo, TEXOMA COMMUNITY CENTER currently holds 0 security badges, indicating that no recognized compliance certifications are currently verified for the organization.
Does TEXOMA COMMUNITY CENTER have SOC 2 Type 1 certification ?
According to Rankiteo, TEXOMA COMMUNITY CENTER is not certified under SOC 2 Type 1.
Does TEXOMA COMMUNITY CENTER have SOC 2 Type 2 certification ?
According to Rankiteo, TEXOMA COMMUNITY CENTER does not hold a SOC 2 Type 2 certification.
Does TEXOMA COMMUNITY CENTER comply with GDPR ?
According to Rankiteo, TEXOMA COMMUNITY CENTER is not listed as GDPR compliant.
Does TEXOMA COMMUNITY CENTER have PCI DSS certification ?
According to Rankiteo, TEXOMA COMMUNITY CENTER does not currently maintain PCI DSS compliance.
Does TEXOMA COMMUNITY CENTER comply with HIPAA ?
According to Rankiteo, TEXOMA COMMUNITY CENTER is not compliant with HIPAA regulations.
Does TEXOMA COMMUNITY CENTER have ISO 27001 certification ?
According to Rankiteo,TEXOMA COMMUNITY CENTER is not certified under ISO 27001, indicating the absence of a formally recognized information security management framework.
Industry Classification of TEXOMA COMMUNITY CENTER
TEXOMA COMMUNITY CENTER operates primarily in the Mental Health Care industry.
Number of Employees at TEXOMA COMMUNITY CENTER
TEXOMA COMMUNITY CENTER employs approximately 104 people worldwide.
Subsidiaries Owned by TEXOMA COMMUNITY CENTER
TEXOMA COMMUNITY CENTER presently has no subsidiaries across any sectors.
TEXOMA COMMUNITY CENTER’s LinkedIn Followers
TEXOMA COMMUNITY CENTER’s official LinkedIn profile has approximately 256 followers.
NAICS Classification of TEXOMA COMMUNITY CENTER
TEXOMA COMMUNITY CENTER is classified under the NAICS code 62133, which corresponds to Offices of Mental Health Practitioners (except Physicians).
TEXOMA COMMUNITY CENTER’s Presence on Crunchbase
No, TEXOMA COMMUNITY CENTER does not have a profile on Crunchbase.
TEXOMA COMMUNITY CENTER’s Presence on LinkedIn
Yes, TEXOMA COMMUNITY CENTER maintains an official LinkedIn profile, which is actively utilized for branding and talent engagement, which can be accessed here: https://www.linkedin.com/company/texoma-community-center.
Cybersecurity Incidents Involving TEXOMA COMMUNITY CENTER
As of December 05, 2025, Rankiteo reports that TEXOMA COMMUNITY CENTER has experienced 1 cybersecurity incidents.
Number of Peer and Competitor Companies
TEXOMA COMMUNITY CENTER has an estimated 5,124 peer or competitor companies worldwide.
What types of cybersecurity incidents have occurred at TEXOMA COMMUNITY CENTER ?
Incident Types: The types of cybersecurity incidents that have occurred include Data Leak.
Incident Details
Can you provide details on each incident ?
Title: Data Breach at Texoma Community Center
Description: Texoma Community Center in Texas (TCC) suffered a data breach incident involving a hack of email that affected about 24,030 patients. The incident involved unauthorized access between September 24, 2020 and December 1, 2020 to several email accounts. The compromised information included name, date of birth, medical history, treatment or diagnosis, health information, health insurance information including policy and/or subscriber information, insurance application and/or claims information, birth certificate, marriage certificate, digital signature, facial photograph, email address and password, unique biometric data, vehicle identification number, username and password, military identification number, and for a smaller number of individuals may include social security number.
Date Detected: September 24, 2020
Type: Data Breach
Attack Vector: Email Hack
What are the most common types of attacks the company has faced ?
Common Attack Types: The most common types of attacks the company has faced is Data Leak.
How does the company identify the attack vectors used in incidents ?
Identification of Attack Vectors: The company identifies the attack vectors used in incidents through Email accounts.
Impact of the Incidents
What was the impact of each incident ?
Incident : Data Breach TEX23212123
Data Compromised: Name, Date of birth, Medical history, Treatment or diagnosis, Health information, Health insurance information, Policy and/or subscriber information, Insurance application and/or claims information, Birth certificate, Marriage certificate, Digital signature, Facial photograph, Email address and password, Unique biometric data, Vehicle identification number, Username and password, Military identification number, Social security number
Systems Affected: Email accounts
What types of data are most commonly compromised in incidents ?
Commonly Compromised Data Types: The types of data most commonly compromised in incidents are Name, Date Of Birth, Medical History, Treatment Or Diagnosis, Health Information, Health Insurance Information, Policy And/Or Subscriber Information, Insurance Application And/Or Claims Information, Birth Certificate, Marriage Certificate, Digital Signature, Facial Photograph, Email Address And Password, Unique Biometric Data, Vehicle Identification Number, Username And Password, Military Identification Number, Social Security Number and .
Which entities were affected by each incident ?
Incident : Data Breach TEX23212123
Entity Name: Texoma Community Center
Entity Type: Healthcare Facility
Industry: Healthcare
Location: Texas, USA
Customers Affected: 24030
Data Breach Information
What type of data was compromised in each breach ?
Incident : Data Breach TEX23212123
Type of Data Compromised: Name, Date of birth, Medical history, Treatment or diagnosis, Health information, Health insurance information, Policy and/or subscriber information, Insurance application and/or claims information, Birth certificate, Marriage certificate, Digital signature, Facial photograph, Email address and password, Unique biometric data, Vehicle identification number, Username and password, Military identification number, Social security number
Number of Records Exposed: 24030
Sensitivity of Data: High
Personally Identifiable Information: namedate of birthmedical historytreatment or diagnosishealth informationhealth insurance informationpolicy and/or subscriber informationinsurance application and/or claims informationbirth certificatemarriage certificatedigital signaturefacial photographemail address and passwordunique biometric datavehicle identification numberusername and passwordmilitary identification numbersocial security number
Initial Access Broker
How did the initial access broker gain entry for each incident ?
Incident : Data Breach TEX23212123
Entry Point: Email accounts
Additional Questions
Incident Details
What was the most recent incident detected ?
Most Recent Incident Detected: The most recent incident detected was on September 24, 2020.
Impact of the Incidents
What was the most significant data compromised in an incident ?
Most Significant Data Compromised: The most significant data compromised in an incident were name, date of birth, medical history, treatment or diagnosis, health information, health insurance information, policy and/or subscriber information, insurance application and/or claims information, birth certificate, marriage certificate, digital signature, facial photograph, email address and password, unique biometric data, vehicle identification number, username and password, military identification number, social security number and .
Data Breach Information
What was the most sensitive data compromised in a breach ?
Most Sensitive Data Compromised: The most sensitive data compromised in a breach were birth certificate, date of birth, medical history, treatment or diagnosis, name, policy and/or subscriber information, email address and password, vehicle identification number, username and password, health insurance information, military identification number, digital signature, unique biometric data, social security number, facial photograph, health information, marriage certificate and insurance application and/or claims information.
What was the number of records exposed in the most significant breach ?
Number of Records Exposed in Most Significant Breach: The number of records exposed in the most significant breach was 270.0.
Initial Access Broker
What was the most recent entry point used by an initial access broker ?
Most Recent Entry Point: The most recent entry point used by an initial access broker was an Email accounts.
.png)
Latest Global CVEs (Not Company-Specific)
Description
Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Prior to 2.0.3, Function api.ParseJSONRequest currently splits (via a call to strings.Split) an optionally-provided OID (which is untrusted data) on periods. Similarly, function api.getContentType splits the Content-Type header (which is also untrusted data) on an application string. As a result, in the face of a malicious request with either an excessively long OID in the payload containing many period characters or a malformed Content-Type header, a call to api.ParseJSONRequest or api.getContentType incurs allocations of O(n) bytes (where n stands for the length of the function's argument). This vulnerability is fixed in 2.0.3.
Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Description
Monkeytype is a minimalistic and customizable typing test. In 25.49.0 and earlier, there is improper handling of user input which allows an attacker to execute malicious javascript on anyone viewing a malicious quote submission. quote.text and quote.source are user input, and they're inserted straight into the DOM. If they contain HTML tags, they will be rendered (after some escaping using quotes and textarea tags).
Risk Information
cvss4
Base: 7.1
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description
SysReptor is a fully customizable pentest reporting platform. Prior to 2025.102, there is a Stored Cross-Site Scripting (XSS) vulnerability allows authenticated users to execute malicious JavaScript in the context of other logged-in users by uploading malicious JavaScript files in the web UI. This vulnerability is fixed in 2025.102.
Risk Information
cvss3
Base: 7.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
Description
Taiko Alethia is an Ethereum-equivalent, permissionless, based rollup designed to scale Ethereum without compromising its fundamental properties. In 2.3.1 and earlier, TaikoInbox._verifyBatches (packages/protocol/contracts/layer1/based/TaikoInbox.sol:627-678) advanced the local tid to whatever transition matched the current blockHash before knowing whether that batch would actually be verified. When the loop later broke (e.g., cooldown window not yet passed or transition invalidated), the function still wrote that newer tid into batches[lastVerifiedBatchId].verifiedTransitionId after decrementing batchId. Result: the last verified batch could end up pointing at a transition index from the next batch (often zeroed), corrupting the verified chain pointer.
Risk Information
cvss4
Base: 8.0
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description
A flaw has been found in youlaitech youlai-mall 1.0.0/2.0.0. Affected is the function getById/updateAddress/deleteAddress of the file /mall-ums/app-api/v1/addresses/. Executing manipulation can lead to improper control of dynamically-identified variables. The attack can be executed remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Risk Information
cvss2
Base: 6.5
Severity: LOW
AV:N/AC:L/Au:S/C:P/I:P/A:P
cvss3
Base: 6.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Access Data Using Our API
Get company history
curl -i -X GET 'https://api.rankiteo.com/underwriter-getcompany-history?linkedin_id=texoma-community-center' -H 'apikey: YOUR_API_KEY_HERE'
RapidWhat Do We Measure ?
Incident
Finding
Grade
Digital Assets
Every week, Rankiteo analyzes billions of signals to give organizations a sharper, faster view of emerging risks. With deeper, more actionable intelligence at their fingertips, security teams can outpace threat actors, respond instantly to Zero-Day attacks, and dramatically shrink their risk exposure window.
These are some of the factors we use to calculate the overall score:
Network Security
Identify exposed access points, detect misconfigured SSL certificates, and uncover vulnerabilities across the network infrastructure.
SBOM (Software Bill of Materials)
Gain visibility into the software components used within an organization to detect vulnerabilities, manage risk, and ensure supply chain security.
CMDB (Configuration Management Database)
Monitor and manage all IT assets and their configurations to ensure accurate, real-time visibility across the company's technology environment.
Threat Intelligence
Leverage real-time insights on active threats, malware campaigns, and emerging vulnerabilities to proactively defend against evolving cyberattacks.
Rankiteo is a unified scoring and risk platform that analyzes billions of signals weekly to help organizations gain faster, more actionable insights into emerging threats. Empowering teams to outpace adversaries and reduce exposure.
